| 2.1 |
Approval of the agenda |
|
| R2-2304600 |
Agenda for RAN2#122 |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2304601 |
RAN2#121bis-e Meeting Report |
MCC |
| R2-2306553 |
RAN2#121bis-e Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2304602 |
RAN2 Handbook |
MCC |
| R2-2305845 |
Further guidelines on UE capability definitions |
Ericsson |
| R2-2306404 |
Discussion on RAN2 signalling alternatives |
Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R2-2306732 |
LS on Signalling alternatives |
RAN2 |
| R2-2306789 |
Further Guidelines on UE capability definitions |
RAN2 |
| R2-2306810 |
Further Guidelines on UE capability definitions |
RAN2 |
| R2-2306914 |
Correction of QoE stage-2 description |
R3 (ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Huawei, CATT, Samsung) |
| R2-2306915 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
R3 (CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom) |
| R2-2306916 |
Modify the figures for MN/SN initiated CPC and CHO with SCG |
R3 (ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Huawei) |
| R2-2306917 |
Correction to Security Issues for MO-SDT |
R3 (China Telecom, ZTE, CATT, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, Huawei) |
| R2-2306950 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
R3 (CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom) |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2304943 |
Correction on handover procedure completion |
vivo, Nokia (rapporteur) |
| R2-2305132 |
Discussion on QoE configuration release in LTE |
Lenovo |
| R2-2306273 |
Correction on QoE configuration release |
Google |
| R2-2306539 |
Correction on QoE configuration release |
Google, Qualcomm, Ericsson |
| R2-2306562 |
Correction on handover procedure completion |
vivo, Nokia (rapporteur) |
| R2-2306563 |
Correction on QoE configuration release |
Google, Qualcomm, Ericsson |
| R2-2306570 |
Correction on handover procedure completion |
vivo, Nokia (rapporteur) |
| R2-2306571 |
Correction on QoE configuration release |
Google, Qualcomm, Ericsson |
| 4.2.0 |
In-Principle-Agreed CRs |
|
| R2-2304762 |
MAC correction on TDD support for IoT NTN |
OPPO |
| R2-2305409 |
Clarification on UL operation upon validity timer expiry for IoT NTN |
Nokia, Nokia Shanghai Bell, Apple, Ericsson |
| R2-2305821 |
Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters |
Nokia, Nokia Shanghai Bell |
| R2-2306064 |
CR to 36.331 on T317 and T318 |
Huawei, HiSilicon |
| R2-2306261 |
Correction for R17 IoT NTN |
Ericsson, OPPO, Thales |
| R2-2306514 |
Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters |
Nokia, Nokia Shanghai Bell |
| R2-2306647 |
Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters |
Nokia, Nokia Shanghai Bell |
| R2-2306648 |
CR to 36.331 on T317 and T318 |
Huawei, HiSilicon |
| R2-2306941 |
Alignment of NPRACH preamble descriptions with RAN1 specification for IoT-NTN parameters |
Nokia, Nokia Shanghai Bell |
| 4.2.1 |
Corrections |
|
| R2-2304763 |
Correction on UL operation upon validity timer expiry in IoT NTN |
OPPO |
| R2-2304810 |
Miscellaneous Stage 2 corrections for IoT NTN |
Huawei, HiSilicon |
| R2-2305760 |
Reference time for the GNSS validity duration IE |
Nokia, Nokia Shanghai Bell |
| R2-2305972 |
Correction on definition of ta-Report |
ZTE Corporation, Sanechips |
| R2-2306041 |
Clarify the reference point for UTC in SIB16 |
MediaTek Inc. |
| R2-2306483 |
RRC correction on PUCCH TX duration |
Samsung Suzhou |
| R2-2306649 |
Miscellaneous Stage 2 corrections for IoT NTN |
Huawei, HiSilicon |
| R2-2306650 |
Correction on definition of ta-Report |
ZTE Corporation, Sanechips |
| R2-2306651 |
IoT NTN RRC Correction on PUCCH TX duration |
Samsung |
| R2-2306668 |
Clarify the reference point for UTC in SIB16 |
MediaTek Inc. |
| R2-2306926 |
[Post122][102][IoT NTN] UTC reference point (Mediatek) |
MediaTek Inc. |
| R2-2306928 |
Miscellaneous Stage 2 corrections for IoT NTN |
Huawei, HiSilicon |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2306002 |
Clarification for on-demand SIB procedure in RRC_CONNECTED |
Ericsson |
| R2-2306003 |
Clarification for on-demand SIB procedure in RRC_CONNECTED |
Ericsson |
| 5.1.1.1 |
Other |
|
| R2-2306412 |
Correction to information delivered in Handover Request message |
Huawei, Nokia (Rapporteur), HiSilicon |
| R2-2306413 |
Correction to information delivered in Handover Request message |
Huawei, Nokia (Rapporteur), HiSilicon |
| R2-2306939 |
Correction to information delivered in Handover Request message |
Huawei, Nokia (Rapporteur), HiSilicon |
| R2-2306940 |
Correction to information delivered in Handover Request message |
Huawei, Nokia (Rapporteur), HiSilicon |
| 5.1.3.0 |
In-Principle-Agreed CRs |
|
| R2-2305394 |
Corrections on refServCellIndicator |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2305395 |
Corrections on refServCellIndicator |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2305396 |
Corrections on refServCellIndicator |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2305468 |
Correction on the need code for secondary DRX group |
Huawei, HiSilicon, Ericsson |
| R2-2305469 |
Correction on the need code for secondary DRX group |
Huawei, HiSilicon, Ericsson |
| R2-2305504 |
Correction on Need code of IE RLC-Config |
Intel Corporation |
| R2-2305505 |
Correction on Need code of IE RLC-Config |
Intel Corporation |
| R2-2305772 |
Clarification on RSSI measurement frequency |
Samsung |
| R2-2305773 |
Clarification on RSSI measurement frequency |
Samsung |
| R2-2305834 |
SIB and PosSIB mappings to SI message |
Ericsson, MediaTek Inc. |
| R2-2305835 |
SIB and PosSIB mappings to SI message |
Ericsson, MediaTek Inc. |
| R2-2305996 |
Clarification on nas-SecurityParamFromNR field description |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2305997 |
Clarification on nas-SecurityParamFromNR field description |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2305998 |
Clarification on nas-SecurityParamFromNR field description |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2306298 |
Miscellaneous Correction on UE capability-R15 |
ZTE Corporation, Sanechips |
| R2-2306299 |
Miscellaneous Correction on UE capability-R16 |
ZTE Corporation, Sanechips |
| R2-2306300 |
Miscellaneous Correction on UE capability-R17 |
ZTE Corporation, Sanechips |
| R2-2306301 |
Correction on PDCCH Blind Detection-R16 |
ZTE Corporation, Sanechips |
| R2-2306302 |
Correction on PDCCH Blind Detection-R17 |
ZTE Corporation, Sanechips |
| R2-2306501 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306502 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306503 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306504 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306765 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306766 |
Correction on pusch-RepetitionTypeB capability |
Huawei, HiSilicon |
| R2-2306932 |
Corrections on refServCellIndicator |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2306933 |
Corrections on refServCellIndicator |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2306936 |
SIB and PosSIB mappings to SI message |
Ericsson, MediaTek Inc. |
| R2-2306937 |
SIB and PosSIB mappings to SI message |
Ericsson, MediaTek Inc. |
| 5.1.3.1 |
NR RRC |
|
| R2-2304746 |
Correction on RRM relaxation and highspeedConfig |
OPPO, ZEKU |
| R2-2304747 |
Correction on RRM relaxation and highspeedConfig |
OPPO, ZEKU |
| R2-2304871 |
Partial resource setup failure at RRC setup |
Nokia, Nokia Shanghai Bell |
| R2-2304872 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2304873 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2304874 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2305133 |
Miscellaneous corrections for Rel-15 RRC |
Lenovo |
| R2-2305134 |
Miscellaneous corrections for Rel-16 RRC |
Lenovo |
| R2-2305411 |
Correction on local release in TS 38.331 |
vivo |
| R2-2305412 |
Correction on local release in TS 38.331 |
vivo |
| R2-2305413 |
Correction on local release in TS 38.331 |
vivo |
| R2-2305831 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2305832 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2305999 |
Clarification on presence of Coreset0 for PSCell |
Ericsson |
| R2-2306000 |
Clarification on presence of Coreset0 for PSCell |
Ericsson |
| R2-2306001 |
Clarification on presence of Coreset0 for PSCell |
Ericsson |
| R2-2306088 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306089 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306090 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306229 |
Correction to time domain resource assignment in NR-U |
Huawei, HiSilicon |
| R2-2306230 |
Correction to time domain resource assignment in NR-U |
Huawei, HiSilicon |
| R2-2306520 |
Clarification on reference cell for TCI state |
Ericsson, Huawei |
| R2-2306526 |
Clarification on reference cell for TCI state |
Ericsson, Huawei |
| R2-2306812 |
Clarification on reference cell for TCI state |
Ericsson, Huawei |
| R2-2306813 |
Clarification on reference cell for TCI state |
Ericsson, Huawei |
| R2-2306815 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306824 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306825 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306826 |
Clarification on UAI for UL MIMO layers |
Huawei, HiSilicon |
| R2-2306831 |
Correction to time domain resource assignment in NR-U |
Huawei, HiSilicon |
| R2-2306908 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2306909 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2306948 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| 5.1.3.2 |
UE capabilities |
|
| R2-2305836 |
Clarification on SRS tx switching capability |
Ericsson, MediaTek Inc. |
| R2-2305837 |
Clarification on SRS tx switching capability |
Ericsson, MediaTek Inc. |
| R2-2305838 |
Clarification on SRS tx switching capability |
Ericsson, MediaTek Inc. |
| R2-2305839 |
Handling of per-UE parameters for NR-DC |
Ericsson |
| R2-2306505 |
Corrections on NR-DC capabilities |
Huawei, HiSilicon |
| R2-2306506 |
Corrections on NR-DC capabilities |
Huawei, HiSilicon |
| R2-2306790 |
Clarification on SRS Tx switching capability |
Ericsson, MediaTek Inc. |
| R2-2306791 |
Clarification on SRS Tx switching capability |
Ericsson, MediaTek Inc. |
| R2-2306792 |
Clarification on SRS Tx switching capability |
Ericsson, MediaTek Inc. |
| 5.2.0 |
In-principle agreed CRs |
|
| R2-2304854 |
Corrections including field description for transmission power |
Huawei, HiSilicon (Rapporteur), ZTE Corporation, Sanechips, CATT |
| R2-2304855 |
Corrections including field description for transmission power |
Huawei, HiSilicon (Rapporteur), ZTE Corporation, Sanechips, CATT |
| R2-2306110 |
Corrections on MAC reset regarding configured sidelink grant |
ASUSTeK, Huawei, HiSilicon, Samsung, vivo |
| R2-2306369 |
Correction for Measurement Event Triggering Criteria |
Sharp Corporation |
| 5.2.1 |
Corrections |
|
| R2-2304829 |
Discussion on future extensibility of sl-FreqInfoList in R16/17 NR SL Spec |
vivo |
| R2-2304850 |
Potential issue caused by using destination index |
Huawei, HiSilicon, vivo |
| R2-2304851 |
Correction on destination index for SL measurement configuration |
Huawei, HiSilicon |
| R2-2304852 |
Correction on destination index for SL measurement configuration |
Huawei, HiSilicon |
| R2-2304853 |
Correction on destination index for SL DRX configuration |
Huawei, HiSilicon |
| R2-2304941 |
Correction on TS 38.304 for NR SL |
vivo |
| R2-2304942 |
Correction on TS 38.304 for NR SL |
vivo |
| R2-2304991 |
Summary on user plane corrections for NR V2X |
LG Electronics Inc. |
| R2-2306701 |
Summary of [AT122][501][V2X/SL] V2X corrections |
vivo (Moderator) |
| 5.3.0 |
In-Principle-Agreed CRs |
|
| R2-2304789 |
Correction on SI update for posSIB-r16 |
Huawei, HiSilicon |
| R2-2304790 |
Correction on SI update for posSIB-r17 |
Huawei, HiSilicon |
| R2-2305253 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305254 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305255 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305256 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305257 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305258 |
APC clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305259 |
Zero Yaw clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305260 |
Zero Yaw clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305261 |
Zero Yaw clarification for SSR positioning |
Swift Navigation, Ericsson |
| R2-2305262 |
Zero Yaw clarification for SSR positioning |
Swift Navigation, Ericsson |
| 5.3.2 |
RRC corrections |
|
| R2-2306409 |
Discussion on the misalignment issue in location measurement indication procedure |
ZTE Corporation |
| R2-2306459 |
Clarification on the misalignment issue in location measurement indication procedure |
ZTE Corporation |
| R2-2306460 |
Clarification on the misalignment issue in location measurement indication procedure |
ZTE Corporation |
| R2-2306461 |
Clarification on the misalignment issue in location measurement indication procedure |
ZTE Corporation |
| 5.3.3 |
LPP corrections |
|
| R2-2306027 |
GNSS Troposperic Delay Correction field description |
Ericsson |
| R2-2306028 |
GNSS Troposperic Delay Correction field description |
Ericsson |
| R2-2306836 |
GNSS Tropospheric Delay Correction field description |
Ericsson |
| R2-2306837 |
GNSS Tropospheric Delay Correction field description |
Ericsson |
| 5.3.4 |
MAC corrections |
|
| R2-2306084 |
Correction on DL MAC CE for SP Positioning SRS |
ZTE Corporation |
| R2-2306085 |
Correction on DL MAC CE for SP Positioning SRS |
ZTE Corporation |
| R2-2306699 |
[AT122][407][POS] Rel-15/16 positioning CR check (Intel) |
Intel Corporation |
| 5.4.3 |
RRC corrections |
|
| R2-2305263 |
Clarification on RLF Cause |
Samsung |
| R2-2305264 |
Clarification on RLF cause |
Samsung |
| R2-2305266 |
Clarification on RLF cause |
Samsung |
| R2-2305980 |
Correction on logging RLM resources in the RLF report |
Ericsson, Qualcomm |
| R2-2305981 |
Correction on logging RLM resources in the RLF report |
Ericsson, Qualcomm |
| R2-2305982 |
Correction to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2305983 |
Correction to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2306037 |
Correction on the release of logged measurement configuration as well as logged measurement information |
QUALCOMM Inc. |
| R2-2306096 |
Discussion on location configuration for SON and MDT features |
Huawei, HiSilicon |
| R2-2306900 |
Correction on the release of logged measurement configuration as well as logged measurement information |
QUALCOMM Inc. |
| R2-2306902 |
Correction to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2306903 |
Correction to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2306938 |
Correction on the release of logged measurement configuration as well as logged measurement information |
QUALCOMM Inc. |
| R2-2306947 |
Correction on the release of logged measurement configuration as well as logged measurement information |
QUALCOMM Inc. |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2304632 |
Reply LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures (R3-232166; contact: ZTE) |
RAN3 |
| 6.1.1.1 |
Other |
|
| R2-2304749 |
Stage-2 correction on BFD and RLM relaxation |
OPPO |
| R2-2305192 |
Miscellaneous Corrections |
Nokia (Rapporteur), Huawei, Qualcomm, Nokia Shanghai Bell |
| R2-2305465 |
Corrections on paging monitoring in eDRX and RRM relaxation for RedCap |
Huawei, HiSilicon |
| R2-2305466 |
Corrections on eDRX and RRM measurement relaxation for RedCap |
Huawei, HiSilicon |
| R2-2305911 |
Clarification for RLM/BFD relaxation when SCG is deactivated |
Ericsson |
| R2-2306344 |
Discussion on Security Issues in MO-SDT |
China Telecom Corporation Ltd. |
| R2-2306345 |
Corrections to Security Issues for MO-SDT |
China Telecom |
| R2-2306776 |
Summary of [AT122][022][RedCap] eDRX RRM relax and sm reception (Huawei) |
Huawei, HiSilicon |
| R2-2306777 |
Corrections on paging monitoring in eDRX |
Huawei, HiSilicon |
| R2-2306778 |
Corrections on eDRX and RRM measurement relaxation for RedCap |
Huawei, HiSilicon |
| R2-2306888 |
Corrections to Security Issues for MO-SDT |
China Telecom |
| R2-2306891 |
Corrections to Security Issues for MO-SDT |
China Telecom, ZTE, vivo, CATT |
| 6.1.2.0 |
In-Principle-Agreed CRs |
|
| R2-2304791 |
Correction to CG-SDT LCH restriction |
Huawei, HiSilicon |
| R2-2305463 |
Corrections on SDT using NCD-SSB for RedCap |
Huawei, HiSilicon |
| R2-2305856 |
Clarification on RA Resource Selection During CG-SDT |
vivo, ZTE Corporation (rapporteur), Sanechips |
| 6.1.2.1 |
Other |
|
| R2-2304727 |
Correction to RA partition selection for Msg1 based SI request |
Samsung Electronics Co., Ltd |
| R2-2304906 |
Correction on SDT with separate initial BWP |
vivo, Huawei, HiSilicon, Guangdong Genius |
| R2-2304907 |
Correction on CG-SDT with NCD-SSB measurement |
vivo |
| R2-2305748 |
Correction on HARQ buffer flush at SCG deactivation |
Nokia, Apple, Mediatek, Qualcomm, Nokia Shanghai Bell |
| R2-2305749 |
Clarification on unknown, unforeseen and erroneous protocol data during SDT |
Nokia, Intel, Mediatek, Nokia Shanghai Bell |
| R2-2306385 |
Correction to carrier selection for RA-SDT |
Langbo |
| R2-2306495 |
Correction on Enhanced BFR MAC CE |
ZTE Corporation, Sanechips |
| R2-2306798 |
Correction on Enhanced BFR MAC CE |
ZTE Corporation, Sanechips |
| R2-2306799 |
Clarification on unknown, unforeseen and erroneous protocol data during SDT |
Nokia, Intel, Mediatek, Nokia Shanghai Bell |
| R2-2306806 |
Correction to RA partition selection for Msg1 based SI request |
Samsung Electronics Co., Ltd |
| R2-2306807 |
Correction on SDT with separate initial BWP |
vivo |
| R2-2306814 |
RA partition selection for Msg1 based SI request |
Samsung |
| 6.1.3.0 |
In-Principle-Agreed CRs |
|
| R2-2304839 |
Miscellaneous corrections for Ext71GHz |
Huawei, HiSilicon |
| R2-2304875 |
Clarification for configured grant periodicity |
Nokia, Nokia Shanghai Bell |
| R2-2304908 |
Correction on measCyclePSCell used during SCG deactivation |
vivo, Ericsson, Huawei, HiSilicon |
| R2-2304982 |
Corrections on the eIAB related capabilities |
Huawei, HiSilicon |
| R2-2304983 |
Correction to MAC reset for eIAB |
Huawei, HiSilicon |
| R2-2305039 |
Correction to RRC for 71 GHz on channel occupancy duration |
Ericsson |
| R2-2305346 |
Clarification to TS 38.331 on Enhanced BFR MAC CE for feMIMO |
CATT |
| R2-2305347 |
Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo |
CATT |
| R2-2305351 |
Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo |
CATT |
| R2-2305433 |
Clarification on the application of slice-based RACH configuration |
Nokia, Huawei |
| R2-2305434 |
Clarification on applicability of slice-based RA |
Huawei, Nokia |
| R2-2305462 |
Corrections on initial BWP configuration and NCD-SSB for RedCap |
Huawei, HiSilicon |
| R2-2305803 |
ResumeCause IE description correction |
Huawei, HiSilicon |
| R2-2305910 |
Corrections for eDRX in RRC_INACTIVE |
Ericsson, Huawei, HiSilicon |
| R2-2306303 |
Miscellaneous Correction on UE capability-R17 |
ZTE Corporation,Sanechips |
| R2-2306494 |
Corrections to on-demand SI request |
ZTE Corporation, Sanechips |
| R2-2306533 |
Addition of slice-based cell re-selection parameters |
Nokia, Nokia Shanghai Bell |
| R2-2306808 |
Correction on scg-State in RRCConnectionReconfiguration including the mobilityControlInfo |
CATT |
| 6.1.3.1 |
NR RRC |
|
| R2-2304610 |
LS to RAN2 on scheduling and HARQ issues for FR2-2 (R1-2304099; contact: LGE) |
RAN1 |
| R2-2304616 |
LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 (R1-2304156; contact: Qualcomm) |
RAN1 |
| R2-2304638 |
Reply LS on support of per FR PRS gap (R4-2306388; contact: Huawei) |
RAN4 |
| R2-2304840 |
Miscellaneous corrections on scheduling and HARQ issues for FR2-2 |
Huawei, HiSilicon |
| R2-2304859 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2304860 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2304939 |
Correction on the applicable NSAG for slice based RACH |
Beijing Xiaomi Software Tech |
| R2-2305047 |
Correction to RRC for 71 GHz on multi-PUSCH |
Ericsson, LG Electronics Inc., ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, Huawei, HiSilicon |
| R2-2305113 |
Discussion on remaining issues for multi-PUSCH |
Ericsson, LG Electronics Inc., ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, Huawei, HiSilicon |
| R2-2305114 |
Further correction to RRC for 71 GHz on multi-PUSCH |
Ericsson, Xiaomi, ASUSTeK, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics Inc |
| R2-2305115 |
Correction to RRC for 71 GHz on scheduling and HARQ issues |
Ericsson |
| R2-2305135 |
Miscellaneous corrections for Rel-17 RRC |
Lenovo |
| R2-2305136 |
Miscellaneous corrections on NR QoE |
Lenovo |
| R2-2305141 |
Addition of multiPDSCH-PerSlot-Type1CB capability definition to 38.306 |
Nokia, Nokia Shanghai Bell |
| R2-2305142 |
Addition of multiPDSCH-PerSlot-Type1CB capability and configuration to 38.331 |
Nokia, Nokia Shanghai Bell |
| R2-2305267 |
CP corrections for 71GHz |
NEC |
| R2-2305268 |
K2 indication for multi-PUSCH |
Qualcomm Incorporated |
| R2-2305348 |
Corrections on R17 unified TCI framework |
CATT |
| R2-2305349 |
Correction on scg-CellGroupConfig within RRC inter-node message |
CATT |
| R2-2305397 |
RedCap 1Rx/2Rx determination from network perspective |
ZTE Corporation, Huawei, Sanechips |
| R2-2305467 |
Corrections on SI request configuration for RedCap |
Huawei, HiSilicon |
| R2-2305470 |
Discussion on the TRS availability |
Huawei, HiSilicon |
| R2-2305489 |
Corrections on the general description of UL information transfer |
CATT |
| R2-2305804 |
Control plane corrections for SDT |
Huawei, HiSilicon |
| R2-2305833 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2305902 |
Correction on RLM/BFD relaxation state reporting |
Nokia, Nokia Shanghai Bell |
| R2-2305912 |
RLM and BFD relaxation and no DRX |
Ericsson |
| R2-2305913 |
Correction on TRS availability |
Ericsson |
| R2-2305968 |
Correction to RRC for 71 GHz on scheduling and HARQ issues |
Ericsson |
| R2-2306061 |
Corrections to gapAssociationPRS |
Huawei, HiSilicon, MediaTek Inc. |
| R2-2306111 |
Correction on TBoMS in multi-PUSCHs list |
ASUSTeK |
| R2-2306220 |
On UAI RLM/BFD reports when “No DRX is used” |
CATT |
| R2-2306318 |
Correction to RRC for 71GHz on scheduling and HARQ configuration for FR2-2 |
LG Electronics Inc. |
| R2-2306354 |
Clarification on scellActiationRS-ConfigToAddModList field description |
Samsung |
| R2-2306388 |
Correction on gapAssociationPRS |
CATT |
| R2-2306496 |
Clarification on SDT configuration |
ZTE Corporation, Sanechips |
| R2-2306782 |
Correction to RRC for 71GHz on scheduling and HARQ configuration for FR2-2 |
LG Electronics Inc., NEC, Huawei, HiSilicon, Ericsson, ASUSTeK, Samsung |
| R2-2306785 |
DRAFT Reply LS on K2 indication for multi-PUSCH |
Qualcomm Incorporated |
| R2-2306809 |
Corrections on R17 unified TCI framework |
CATT |
| R2-2306811 |
Correction on gapAssociationPRS |
CATT, Huawei, HiSilicon, MediaTek Inc., ZTE, Sanechips |
| R2-2306816 |
Reply LS on K2 indication for multi-PUSCH |
RAN2 |
| R2-2306830 |
Correction on the applicable NSAG for slice based RA procedure |
Xiaomi |
| R2-2306869 |
Correction on scg-CellGroupConfig within RRC inter-node message |
CATT |
| R2-2306877 |
[DRAFT] Reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 |
Qualcomm |
| R2-2306878 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2306879 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2306890 |
Miscellaneous corrections on NR QoE |
Lenovo |
| R2-2306892 |
Reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 |
RAN2 |
| R2-2306910 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| R2-2306943 |
Correction on the applicable NSAG for slice based RA procedure |
Xiaomi |
| R2-2306949 |
Miscellaneous non-controversial corrections Set XVIII |
Ericsson |
| 6.1.3.2 |
UE capabilities |
|
| R2-2304611 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112bis-e (R1-2304115; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2304633 |
LS on updated Rel-17 RAN4 UE feature list for NR (R4-2304660; contact: CMCC) |
RAN4 |
| R2-2304670 |
Discussion on ue-PowerClassPerBandPerBC-r17 |
OPPO |
| R2-2304856 |
Maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated, Apple, Ericsson |
| R2-2304857 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated |
| R2-2304858 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated |
| R2-2305108 |
Way forward on agg BW reporting per BC |
Apple |
| R2-2305270 |
Corrections to signaling of Rel-17 channel bandwidths in FR1 |
Qualcomm Incorporated |
| R2-2305464 |
Correction on the capability of RedCap UE |
Huawei, HiSilicon |
| R2-2305875 |
Discussion on per-band per-BC power class capability signalling |
Nokia, Nokia Shanghai Bell |
| R2-2305876 |
Discussion on per-band per-BC power class capability signalling |
Nokia, Nokia Shanghai Bell |
| R2-2305877 |
Clarification on ue-PowerClassPerBandPerBC-r17 |
Nokia, Nokia Shanghai Bell |
| R2-2305950 |
Miscellaneous updates for TR 38.822 |
Intel Corporation |
| R2-2306322 |
Alignment with RAN1 feature list update on MBS |
Intel Corporation |
| R2-2306499 |
On signaling for the maximum aggregated bandwidth |
MediaTek Inc. |
| R2-2306507 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306508 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306509 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306510 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306511 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306512 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306820 |
Miscellaneous updates for TR 38.822 |
Intel Corporation |
| R2-2306835 |
Correction on the capability of RedCap UE |
Huawei, HiSilicon |
| R2-2306885 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306886 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306887 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| R2-2306921 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc |
| 6.1.3.3 |
Other |
|
| R2-2304984 |
Corrections on RLF indication for BAP |
Huawei, HiSilicon |
| R2-2305415 |
Relation between slice-based reselection information provided in dedicated signalling and SIB16 |
Nokia, Nokia Shanghai Bell, Ericsson, Kyocera |
| R2-2305782 |
Clarification on Access Identities Validity |
Samsung R&D Institute India |
| R2-2305798 |
Clarification on respective roles of MAC and RRC in configuring various IAB parameters |
Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Huawei |
| R2-2306004 |
Clarification on which CSI-RS resources in IAB restricted beam MAC CEs |
Ericsson |
| R2-2306005 |
Correction on number of restricted beams for eIAB - Alt1 |
Ericsson |
| R2-2306006 |
Correction on number of restricted beams for eIAB - Alt2 |
Ericsson |
| R2-2306099 |
Discussion on the relation between SIB16 and dedicated signalling |
Huawei, HiSilicon |
| R2-2306174 |
Essentiality of SIB16 in RAN Slicing |
Apple, OPPO |
| R2-2306395 |
Correction on handling on slice availability in SIB16 in TS 38.304 |
CATT,Samsung,Xiaomi, Spreadtrum, Apple,OPPO |
| R2-2306431 |
Corrections on RRM relaxation for RedCap |
Huawei, HiSilicon, OPPO |
| R2-2306834 |
Clarifications on the use of SIB16 |
Nokia, Nokia Shanghai Bell, Ericsson, Kyocera |
| R2-2306867 |
Clarification on Access Identities Validity |
Samsung |
| R2-2306868 |
Clarification on Access Identities Validity |
Samsung |
| R2-2306872 |
Clarification on which CSI-RS resources in IAB restricted beam MAC CEs |
Ericsson |
| R2-2306880 |
Clarifications on the use of SIB16 |
Nokia, Nokia Shanghai Bell, Ericsson, Kyocera |
| R2-2306893 |
Clarification on which CSI-RS resources in IAB restricted beam MAC CEs |
Ericsson |
| R2-2306935 |
Clarification on respective roles of MAC and RRC in configuring various IAB parameters |
Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Huawei |
| R2-2306945 |
Clarification on Access Identities Validity |
Samsung |
| R2-2306946 |
Clarification on Access Identities Validity |
Samsung |
| 6.2.0 |
In principle agreed CRs |
|
| R2-2304721 |
Corrections to paging for MBS |
Samsung Electronics Co., Ltd |
| R2-2304780 |
Corrections on MBS Broadcast Configuration |
CATT, CBN |
| R2-2304781 |
Correction on Supporting MBS in SNPN |
CATT, CBN |
| R2-2304782 |
Correction on Supporting MBS in SNPN |
CATT, CBN |
| R2-2304815 |
Miscellaneous RRC corrections for MBS |
Huawei, HiSilicon |
| R2-2304816 |
Correction on MBS capabilities |
Huawei, HiSilicon |
| R2-2304981 |
Corrections on cfr-ConfigMulticast and Multicast DRX |
NEC, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2305662 |
Misc correction to TS 38.331 on NR MBS |
ZTE, Sanechips |
| R2-2305771 |
Corrections on SPS Initialization and Handling of Unknown, Unforeseen and Erroneous Protocol Data for MBS |
Samsung R&D Institute India |
| R2-2305847 |
Correction to PDSCH Aggregation of MBS SPS |
vivo |
| R2-2306112 |
Corrections on MBS SPS configuration |
ASUSTeK |
| R2-2306581 |
Corrections on MBS Broadcast Configuration |
CATT, CBN |
| R2-2306582 |
Corrections on SPS Initialization and Handling of Unknown, Unforeseen and Erroneous Protocol Data for MBS |
Samsung |
| R2-2306583 |
Correction on Supporting MBS in SNPN |
CATT, CBN |
| R2-2306584 |
Corrections on cfr-ConfigMulticast and Multicast DRX |
NEC, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2306585 |
Correction to mtch-neighbourCell field description |
ZTE, Sanechips |
| R2-2306586 |
Correction to PDSCH Aggregation of MBS SPS |
vivo |
| R2-2306587 |
Miscellaneous RRC corrections for MBS |
Huawei, HiSilicon |
| R2-2306852 |
Corrections to paging for MBS |
Samsung, Xiaomi |
| 6.2.1 |
CP and Stage-2 corrections |
|
| R2-2304697 |
Discussion on MBS Broadcast Reception on SCell |
vivo Mobile Com. (Chongqing) |
| R2-2304776 |
Discussion on plmn-Index with MBS broadcast reception on SCell |
CATT, CBN |
| R2-2304777 |
Corrections on pdsch-HARQ-ACK-CodebookListMulticast |
CATT, CBN |
| R2-2304817 |
Remaining CP issues for MBS |
Huawei, CBN, HiSilicon |
| R2-2304987 |
Correction on terminology misalignment in 38.300 |
NEC |
| R2-2305584 |
Corrections for MBS paging |
Xiaomi |
| R2-2305914 |
Clarification for Mission Critical UEs |
Ericsson |
| R2-2305915 |
MBS broadcast on SCell using plmn-Index |
Ericsson |
| R2-2306113 |
Discussion on SPS deactivation state list for MBS |
ASUSTeK |
| R2-2306114 |
Corrections on SPS deactivation state list for MBS |
ASUSTeK |
| R2-2306323 |
Supporting MBS Broadcast reception in SCell |
Samsung |
| R2-2306359 |
MBS Scell Reception |
Nokia, Nokia Shanghai Bell |
| R2-2306589 |
Correction for using PLMN index in MCCH of Scell |
CATT, Ericsson, Samsung |
| R2-2306819 |
Corrections for MBS paging |
Xiaomi |
| R2-2306927 |
Correction for PLMN index in MCCH of SCell |
CATT, Ericsson, Samsung |
| 6.2.2 |
UP corrections |
|
| R2-2304699 |
Further Correction on Multicast DRX without cfr-ConfigMulticast |
vivo, NEC Corporation |
| R2-2304818 |
Remaining issue on PTP retransmission monitoring |
Huawei, CBN, HiSilicon |
| R2-2305737 |
DRX Timers for PTP Retransmission |
Samsung |
| R2-2306320 |
Correction to SDAP protocol for NR MBS |
TD Tech, Chengdu TD Tech |
| R2-2306360 |
MBS General CR to 38.331 |
Nokia, Nokia Shanghai Bell |
| R2-2306392 |
PTM retransmission reception by UEs without HARQ feedback |
Nokia, Nokia Shanghai Bell |
| R2-2306588 |
Correction on the start condition of drx-HARQ-RTT-TimerDL |
Huawei, HiSilicon |
| R2-2306850 |
Corrections for PTM retransmission reception for multicast DRX with HARQ feedback disabled |
Nokia, Nokia Shanghai Bell |
| R2-2306851 |
Corrections for PTM retransmission reception for multicast DRX with HARQ feedback disabled |
Nokia, Nokia Shanghai Bell |
| R2-2306853 |
PTM retransmission reception by UEs without HARQ feedback |
Nokia, Nokia Shanghai Bell |
| 6.3.0 |
In principle agreed CRs |
|
| R2-2306196 |
Clarification on the services expected from SRAP layer |
Huawei, HiSilicon |
| R2-2306197 |
Clarification on the maximum Data field size for L2 U2N relay |
Huawei, HiSilicon |
| R2-2306198 |
Clarification on sidelink communication resource configuration used by OoC L2 Remote UE |
Huawei, HiSilicon |
| R2-2306199 |
Miscellaneous corrections for SL relay |
Huawei, HiSilicon, CATT, ZTE Corporation, Sanechips, vivo, Apple, Nokia, Nokia Shanghai Bell, Philips International B.V. |
| 6.3.1 |
Control plane and Stage-2 corrections |
|
| R2-2305058 |
Miscellaneous corrections for Stage 2 NR sidelink relay |
Apple |
| R2-2305059 |
Correction on field description of sl-DestinationIdentityL2U2N |
Apple |
| R2-2305060 |
Corrections on triggering conditons of SUI message for SL relay |
Apple |
| R2-2305212 |
Clarification on sidelink discovery |
ZTE, Sanechips |
| R2-2305215 |
Correction on remote UE’s behavior upon SIB1 reception |
Xiaomi |
| R2-2305243 |
UE behavior when the NW indicates not supporting discovery |
vivo |
| R2-2305244 |
Correction on L2 U2N Relay UE behavior upon cell selection |
vivo |
| R2-2305274 |
Correction on direct to indirect path switching |
CATT |
| R2-2305275 |
Correction on the PC5 unicast link release in case of indirect to direct path switching |
CATT |
| R2-2305573 |
On sidelink discovery transmission upon reception of SIB12 |
Nokia, Nokia Shanghai Bell |
| R2-2305587 |
Differentiation of SD-RSRP and SL-RSRP |
Nokia, Nokia Shanghai Bell |
| R2-2305820 |
Non NBC change to SL DRX timers BWP numerology |
Nokia, Nokia Shanghai Bell |
| R2-2305846 |
Reception of PC5 release message during re-establishment |
Lenovo |
| R2-2305849 |
Correction for release message with re-establishment |
Lenovo |
| R2-2306115 |
Corrections on L2 U2N Relay |
ASUSTeK |
| R2-2306131 |
Correction on Sidelink Relay discovery procedure |
Philips International B.V. |
| R2-2306194 |
RRC corrections for SL Relay |
Huawei, HiSilicon |
| R2-2306498 |
Correction on Sidelink Discovery Transmissions |
Ericsson España S.A. |
| R2-2306682 |
Miscellaneous corrections for Stage 2 NR sidelink relay |
Apple, CATT, Nokia, Nokia Shanghai Bell |
| R2-2306683 |
Report of [AT122][411][Relay] NOTE on remote UE reception of SIB1 (Huawei) |
Huawei, HiSilicon |
| R2-2306684 |
Clarification on remote UE reception of SIB1 |
Huawei, HiSilicon, Xiaomi |
| R2-2306685 |
On sidelink discovery transmission upon reception of SIB12 |
Nokia, Nokia Shanghai Bell |
| R2-2306687 |
RRC corrections for SL Relay |
Huawei, HiSilicon, ASUSTeK, Apple |
| R2-2306688 |
[AT122][414][Relay]Handling of PC5 connection release during RRC re-establishment (Lenovo) |
Lenovo (Rapporteur) |
| R2-2306689 |
Handling of PC5 connection release during RRC re-establishment |
Lenovo |
| R2-2306751 |
[Pre122][406][Relay] Summary of AI 6.3.1 on Rel-17 relay control plane (Huawei) |
Huawei, HiSilicon |
| R2-2306840 |
Handling of PC5 connection release during RRC re-establishment |
Lenovo |
| R2-2306844 |
Clarification on remote UE reception of SIB1 |
Huawei, HiSilicon, Xiaomi |
| R2-2306845 |
Sidelink discovery transmission upon reception of SIB12 |
Nokia, Nokia Shanghai Bell |
| R2-2306883 |
Report of [AT122][411][Relay] NOTE on remote UE reception of SIB1 (Huawei) |
Huawei, HiSilicon |
| 6.3.2 |
User plane corrections |
|
| R2-2305211 |
Corrections on SRAP for SL relay |
ZTE Corporation, Sanechips |
| R2-2305589 |
Corrections on SRAP for SL relay |
NEC, Apple, Samsung, ZTE |
| R2-2306195 |
Clarification on the SRAP configuration used in SRAP |
Huawei, HiSilicon |
| R2-2306679 |
Corrections on SRAP for SL relay |
ZTE, Sanechips, Samsung, OPPO, Apple |
| R2-2306680 |
Clarification on the SRAP configuration used in SRAP |
Huawei, HiSilicon |
| R2-2306698 |
Report of [AT122][410][Relay] SRAP corrections (ZTE) |
ZTE Corporation, Sanechips |
| R2-2306934 |
Corrections on SRAP for SL relay |
NEC, Apple, Samsung, ZTE |
| 6.4.0 |
In principle agreed CRs |
|
| R2-2304730 |
Correction on missing referencing of the NTN spec in 38.306 |
Mediatek India Technology Pvt. |
| R2-2304761 |
NTN stage-2 correction |
OPPO, Ericsson, Thales, Samsung |
| R2-2304828 |
Correction on Event D1 for Rel-17 NTN |
vivo |
| R2-2304866 |
Correction on missing referencing of the NTN spec in 38.306 |
MediaTek |
| R2-2304867 |
Correction on missing referencing of the NTN spec in 38.331 |
MediaTek |
| R2-2304869 |
Correction on missing referencing of the NTN spec in 38.306 |
MediaTek |
| R2-2304870 |
Correction on missing referencing of the NTN spec in 38.331 |
MediaTek |
| R2-2304929 |
Corrections to NR NTN for 38.321 |
CATT, Turkcell, Huawei, HiSilicon, Quectel, CAICT, Ericsson |
| R2-2305503 |
Correction on NR NTN UE capabilities |
Intel Corporation |
| R2-2306116 |
Clarification on T430 handling for target cell |
ASUSTeK, Samsung, Huawei, HiSilicon |
| R2-2306117 |
Correction on MIB configuration for NR NTN |
ASUSTeK |
| R2-2306152 |
Clarification on UL operation upon validity timer expiry |
Apple, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, LG Electronics Inc. |
| R2-2306356 |
Correction on SMTC for NR NTN |
Samsung, Huawei, HiSilicon, Google |
| R2-2306652 |
Correction on missing referencing of the NTN spec in 38.306 |
MediaTek |
| R2-2306653 |
Correction on missing referencing of the NTN spec in 38.331 |
MediaTek |
| R2-2306654 |
Corrections to NR NTN for 38.321 |
CATT, Turkcell, Huawei, HiSilicon, Quectel, CAICT, Ericsson |
| R2-2306655 |
NTN stage-2 correction |
OPPO, Ericsson, Thales, Samsung |
| R2-2306656 |
Correction on SMTC for NR NTN |
Samsung, Huawei, HiSilicon, Google |
| R2-2306663 |
Correction on MIB configuration for NR NTN |
ASUSTeK, Sequans, Ericsson |
| R2-2306667 |
NTN stage-2 correction |
OPPO, Ericsson, Thales, Samsung, LG Electronics, Qualcomm, CATT, Huawei, Lenovo |
| 6.4.1 |
Corrections |
|
| R2-2304639 |
Reply LS on enhanced cell reselection in NTN (R4-2306389; contact: Nokia) |
RAN4 |
| R2-2304837 |
Correction on stage-2 descriptions for measurement in NR NTN |
vivo |
| R2-2304868 |
Correction on actual SMTC offset for multiple NTN-Configs |
MediaTek |
| R2-2304892 |
Clarification on the SFTD applicability for NTN cell |
CATT, Qualcomm Incorporated, THALES, Quectel, Turkcell, IPLOOK |
| R2-2305193 |
Clarification on TN EUTRA capability reporting |
Qualcomm Incorporated |
| R2-2305376 |
NTN stage-2 correction |
OPPO, LG Electronics, Qualcomm, CATT, Huawei, Lenovo, Thales |
| R2-2305378 |
MAC and RRC corrections for NR NTN |
OPPO |
| R2-2305497 |
Different UE capability support between TN and NTN |
Intel Corporation, Qualcomm Inc., Nokia, MediaTek, OPPO, vivo, Xiaomi, Apple, Thales, Lenovo, Samsung |
| R2-2305878 |
Missing reference to cell reselection requirements for NTN UEs in RRC INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2306063 |
CR to 38.331 on Event D1 |
Huawei, HiSilicon |
| R2-2306251 |
Clarification on configuration upon TN NTN mobility in RRC_INACTIVE |
Ericsson |
| R2-2306262 |
Description of R17 NR NTN HARQ mode A and B |
Ericsson |
| R2-2306657 |
Summary of [AT122][107][NR-NTN] CR0668 (vivo) |
vivo (Moderator) |
| R2-2306658 |
NTN stage-2 correction |
OPPO, LG Electronics, Qualcomm, CATT, Huawei, Lenovo, Thales |
| R2-2306659 |
Missing reference to cell reselection requirements for NTN UEs in RRC INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2306660 |
Clarification on TN EUTRA capability reporting |
Qualcomm Inc. |
| R2-2306661 |
Different UE capability support between TN and NTN |
Intel Corporation, Qualcomm Inc., Nokia, MediaTek, OPPO, vivo, Xiaomi, Apple, Thales, Lenovo, Samsung, Ericsson |
| R2-2306662 |
Correction on the description of kmac |
OPPO |
| 6.5.0 |
In principle agreed CRs |
|
| R2-2304792 |
Correction to UEPositioningAssistanceInformation |
Huawei, HiSilicon |
| R2-2304884 |
Measurements and Assistance Data Transfer |
Nokia, Nokia Shanghai Bell |
| R2-2304885 |
Protection Level and Target Integrity Risk |
Nokia, Nokia Shanghai Bell |
| R2-2304886 |
LOS-NLOS-Indicator Types |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2305131 |
Miscellaneous corrections on LPP |
Lenovo |
| R2-2305289 |
Corrections on applicability of timing error margin of RxTEG in NR-Multi-RTT-SignalMeasurementInformation field descriptions and other Miscellaneous corrections |
CATT |
| R2-2305290 |
Corrections on the figure of UE Positioning Assistance Information procedure |
CATT |
| R2-2305291 |
Miscellaneous corrections on 38.305 |
CATT |
| R2-2305444 |
Stage 2 procedure for deactivation of MG gap and PPW |
Intel Corporation |
| R2-2305445 |
LPP capability for FGs27-13a,14a and 14-2 |
Intel Corporation |
| R2-2306018 |
Update of information transfer from gNB to LMF |
Ericsson |
| 6.5.1 |
Corrections |
|
| R2-2304608 |
LS on GNSS integrity requirement parameters definition (C4-230655; contact: Huawei) |
CT4 |
| R2-2304802 |
Correction on PosSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 |
Huawei, HiSilicon |
| R2-2304803 |
Correction to MAC spec for Positoning Enhancements |
Huawei, HiSilicon, Ericsson, ZTE |
| R2-2304804 |
Reply to CT4 on GNSS integrity requirements |
Huawei, HiSilicon |
| R2-2305363 |
Correction on PosSRS-RRC-Inactive-OutsideInitialUL-BWP |
Huawei, HiSilicon |
| R2-2305895 |
Miscelaneous LPP Corrections |
Qualcomm Incorporated (Rapporteur) |
| R2-2306025 |
Miscellaneous corrections and additions |
Ericsson, Fraunhofer IIS, Fraunhofer HHI |
| R2-2306026 |
Missing finer periodicities than 1s |
Ericsson |
| R2-2306086 |
Correction on Location measurement indication for positioning |
ZTE Corporation |
| R2-2306087 |
Discussion on Location measurement indication for positioning |
ZTE Corporation |
| R2-2306258 |
Alert Limit |
Nokia, Nokia Shanghai Bell |
| R2-2306259 |
NR-TRP-LocationInfo for UE-based DL-TDOA and DL-AoD positioning |
Nokia, Nokia Shanghai Bell |
| R2-2306676 |
Miscelaneous LPP Corrections |
Qualcomm Incorporated (Rapporteur) |
| R2-2306677 |
Correction to MAC spec for Positoning Enhancements |
Huawei, HiSilicon, Ericsson, ZTE |
| R2-2306678 |
Alert Limit |
Nokia, Nokia Shanghai Bell |
| R2-2306681 |
Reply LS on GNSS integrity parameters |
RAN2 |
| R2-2306756 |
[Pre122][407][POS] Summary of AI 6.5.1 on Rel-17 positioning |
CATT |
| 6.6.1 |
SON Corrections |
|
| R2-2305417 |
Correction to NR M3 measurement |
Nokia, Nokia Shanghai Bell |
| R2-2305418 |
Correction to timeSCGFailure |
Nokia, Nokia Shanghai Bell |
| R2-2305482 |
Correction on timeSinceCHO-Reconfig in TS 38.331 |
CATT |
| R2-2305984 |
Correction to the handling of RLF-Report after successful HO |
Ericsson |
| R2-2305985 |
Miscellaneous corrections on SHR |
Ericsson |
| R2-2306034 |
NB-IoT UE location Info in RLF report |
Qualcomm Incorporated |
| R2-2306035 |
Correction on UE location information in NB-IoT RLF report |
Qualcomm Inc. |
| R2-2306394 |
Correction on SCG failure scenario of MHI in TS 38.331 |
CATT |
| R2-2306822 |
Correction to timeSCGFailure |
Nokia, Nokia Shanghai Bell |
| R2-2306847 |
Correction to the handling of RLF-Report after successful HO |
Ericsson |
| R2-2306899 |
Correction to timeSCGFailure |
Nokia, Nokia Shanghai Bell |
| 6.6.2 |
MDT Corrections |
|
| R2-2304635 |
LS on Excess Packet Delay Threshold for MDT (S5-232150; contact: Nokia) |
SA5 |
| R2-2304655 |
Reply LS on the user consent for trace reporting (S3-231398; contact: Huawei) |
SA3 |
| R2-2306097 |
Discussion on the UL PDCP packet average delay measurement of split bearer |
Huawei, HiSilicon |
| R2-2306098 |
Stage-2 correction on the UL PDCP packet average delay |
Huawei, HiSilicon |
| R2-2306474 |
Report of new packet loss rate |
China Unicom |
| R2-2306475 |
38.314 CR for the introduction of packet loss rate with delay threshold |
China Unicom, CATT |
| R2-2306931 |
Packet loss rate with delay threshold |
China Unicom, CATT |
| 6.7.0 |
In-principle agreed CRs |
|
| R2-2304760 |
Correction on the usage of default CBR values for NR sidelink |
OPPO, Xiaomi, CATT |
| R2-2304843 |
Miscellaneous corrections on 38.331 for SL enhancements |
Huawei, HiSilicon (Rapporteur), Xiaomi |
| R2-2306177 |
Corrections on MAC reset regarding configured sidelink grant |
ASUSTeK, Huawei, HiSilicon, Samsung, vivo |
| 6.7.1 |
General and Stage 2 corrections |
|
| R2-2304844 |
Corrections on TS 38.300 for SL enhancements |
Huawei, HiSilicon |
| R2-2304846 |
Corrections on TS 38.304 for SL enhancements |
Huawei, HiSilicon |
| R2-2305057 |
Miscellaneous corrections for Stage 2 NR sidelink enhancements |
Apple |
| R2-2305111 |
Correction to 38300 on IUC |
Ericsson, Apple |
| R2-2305112 |
Correction to 38300 on IUC cast type |
Ericsson |
| R2-2305225 |
Miscellaneous corrections on TS 38.300 for NR sidelink |
Xiaomi |
| R2-2306704 |
[AT122][502][V2X/SL] 38.300 corrections (Xiaomi) |
[AT122][502][V2X/SL] 38.300 corrections (Xiaomi) |
| R2-2306705 |
Miscellaneous corrections on TS 38.300 for NR sidelink |
Xiaomi |
| R2-2306864 |
Miscellaneous corrections on TS 38.300 for NR sidelink |
Xiaomi, Huawei, HiSilicon, Ericsson, Apple |
| 6.7.2 |
Control plane corrections |
|
| R2-2304940 |
Corrections on TS 38.304 for NR SL enhancement |
vivo |
| R2-2305276 |
Consideration on the time length for DRX timers |
CATT |
| R2-2305277 |
Correction on the time length for DRX timers |
CATT |
| R2-2306118 |
Discussion on deriving timer length for DRX timers |
ASUSTeK, vivo, ZTE Corporation, Sanechips |
| R2-2306119 |
Corrections on deriving timer length for DRX timers (option 1a) |
ASUSTeK, ZTE Corporation, Sanechips |
| R2-2306257 |
Corrections on deriving timer length for DRX timers by relying on DCI format 3_0 (option 1b) |
vivo |
| R2-2306706 |
Corrections on deriving timer length of DRX timers for SL |
ASUSTeK, ZTE Corporation, Sanechips, vivo |
| R2-2306707 |
Summary on [AT122][504][V2X/SL] 38.304 correction (Huawei) |
Huawei |
| R2-2306708 |
Corrections on TS 38.304 for SL enhancements |
Huawei, HiSilicon, vivo, ZTE, Sanechips |
| 6.7.3 |
User plane corrections |
|
| R2-2304845 |
Correction on 38.321 for SL enhancements |
Huawei, HiSilicon |
| R2-2304995 |
Summary on user plane corrections for NR SL enhancements |
LG Electronics Inc. |
| R2-2305224 |
Discussion on the usage of default CBR values for exceptional pool |
Xiaomi |
| R2-2305226 |
Miscellaneous corrections on TS 38.321 for NR sidelink |
Xiaomi |
| R2-2305278 |
Correction on resource (re-)selection for NR sidelink |
CATT |
| R2-2306311 |
MAC PDU filtering |
Nokia, Nokia Shanghai Bell |
| R2-2306709 |
Summary of [AT122][505][V2X/SL] 38.321 Corrections (LG) |
LG |
| R2-2306710 |
MAC PDU filtering |
Nokia, Nokia Shanghai Bell |
| R2-2306849 |
MAC PDU filtering |
Nokia, Nokia Shanghai Bell |
| R2-2306942 |
MAC PDU filtering |
Nokia, Nokia Shanghai Bell |
| R2-2306944 |
MAC PDU filtering |
Nokia, Nokia Shanghai Bell |
| 7.1.1 |
Organizational |
|
| R2-2305400 |
RRC running CR for R18 NCR |
ZTE Corporation |
| R2-2305795 |
Introducing support for Network Controlled Repeaters to 38.321 |
Samsung |
| R2-2305951 |
UE capabilities for NCR |
Intel Corporation |
| R2-2305952 |
UE capabilities for NCR |
Intel Corporation |
| R2-2306235 |
38.304 running CR for R18 NCR |
CATT |
| R2-2306434 |
38.300 Running CR for NCR |
Ericsson |
| R2-2306601 |
Introducing support for Network Controlled Repeaters to 38.331 |
ZTE Corporation |
| R2-2306602 |
Introducing support for Network Controlled Repeaters to 38.321 |
Samsung |
| R2-2306603 |
UE capabilities for NCR |
Intel Corporation |
| R2-2306604 |
UE capabilities for NCR |
Intel Corporation |
| R2-2306605 |
38.304 CR for R18 NCR |
CATT |
| R2-2306606 |
38.300 Running CR for NCR |
Ericsson |
| R2-2306607 |
LS on applicability of UAC for Network Controlled Repeater |
RAN2 |
| R2-2306608 |
Introducing support for Network Controlled Repeaters to 38.321 |
Samsung |
| R2-2306609 |
Introducing support for Network Controlled Repeaters to 38.331 |
ZTE Corporation |
| R2-2306610 |
38.304 CR for R18 NCR |
CATT |
| R2-2306611 |
LS on applicability of UAC for Network Controlled Repeater |
RAN2 |
| R2-2306894 |
Summary of discussion [AT122][705][NCR] MAC CR for NCR (Samsung) |
Samsung |
| 7.1.2 |
Signalling for side control information |
|
| R2-2304962 |
Discussion on UL backhaul link beam indication |
Fujitsu |
| R2-2305402 |
Remaining issue for side control information |
ZTE Corporation, Sanechips |
| R2-2306181 |
On MAC CE for Joint TCI State Indication |
vivo |
| R2-2306560 |
[Pre122][701][NCR] Summary of AI 7.1.2 on signalling for SCI |
Fujitsu Limited |
| 7.1.3 |
Other RAN2 aspects |
|
| R2-2304824 |
Discussion on the remaining CP issues for NCR |
Huawei, HiSilicon |
| R2-2304825 |
Discussion on NCR-MT capability |
Huawei, HiSilicon |
| R2-2305051 |
NCR access link beam update capability |
Nokia, Nokia Shanghai Bell |
| R2-2305052 |
NCR remaining RRM issues |
Nokia, Nokia Shanghai Bell |
| R2-2305061 |
Discussion on remaining issues for NCR |
Apple |
| R2-2305157 |
TPs to 38304 and 3833 on NCR operation |
Qualcomm Inc. |
| R2-2305356 |
Discussion on NCR remaining open issues |
NEC |
| R2-2305401 |
Discussion on NCR open issues |
ZTE Corporation, Sanechips |
| R2-2305501 |
Discussion on NCR remaining open issues |
Intel Corporation |
| R2-2305694 |
Discussion on RRC states for NCR-MT |
Lenovo |
| R2-2306029 |
Discussion on NCR operation (TPs to 38304 and 38331) |
Qualcomm Inc. |
| R2-2306050 |
Discussion on wake-up timer solution |
Fujitsu |
| R2-2306139 |
Considerations on short term link failure on NCR backhaul link |
Samsung R&D Institute UK |
| R2-2306151 |
Remaining issues on NCR |
Kyocera |
| R2-2306182 |
Discussion on Support of RRC_IDLE |
vivo |
| R2-2306340 |
Consideration on remaining issues for NCR |
China Telecom Corporation Ltd. |
| R2-2306435 |
Remaining issues for NCR |
Ericsson |
| R2-2306436 |
Discussion on transitioning from IDLE to CONNECTED |
Ericsson |
| R2-2306487 |
Further considerations on NCR procedures |
Samsung Suzhou |
| R2-2306758 |
[Pre122][702][NCR] Summary of AI 7.1.3 on other RAN2 aspects |
ZTE Corporation |
| 7.2.1 |
Organizational |
|
| R2-2304614 |
Reply LS to RAN2 on error source distributions (R1-2304147; contact: InterDigital) |
RAN1 |
| R2-2304615 |
Reply LS on RAN dependency for Ranging & Sidelink Positioning (R1-2304152; contact: Xiaomi) |
RAN1 |
| R2-2304647 |
LS on support of multiple Target UEs (S2-2303837; contact: Qualcomm) |
SA2 |
| R2-2304650 |
Reply LS to Reply LS to LS on SL positioning groupcast and broadcast (S2-2305726; contact: Xiaomi) |
SA2 |
| R2-2304651 |
Reply LS to LS to SA2 on Sidelink positioning procedure (S2-2305735; contact: Xiaomi) |
SA2 |
| R2-2304657 |
Reply LS on LPP message and supplementary service event report over a user plane connection between UE and LMF and LS on UE event reporting over a user plane connection to LCS client or AF (S3-232232; contact: Ericsson) |
SA3 |
| R2-2304769 |
LPP running CR for RAT-dependent integrity |
CATT |
| R2-2305438 |
Further considerations on SLPP specification |
Intel Corporation |
| R2-2305439 |
TS 38.355 v0.0.3 |
Intel Corporation |
| R2-2305729 |
Draft Reply LS to SA2 on Sidelink positioning procedure |
Xiaomi |
| R2-2305896 |
Running Stage 2 CR for 'Expanded and improved NR positioning' |
Qualcomm Incorporated |
| R2-2306253 |
Work Plan on Rel-18 Positioning Work Item |
CATT, Intel Corporation, Ericsson |
| R2-2306387 |
Support of Multiple Target UEs for Sidelink Positioning (draft response LS to R2-2302448 (S2-2303837)) |
Qualcomm Incorporated |
| 7.2.2 |
Sidelink positioning |
|
| R2-2304716 |
Discussion of signalling procedures |
Nokia, Nokia Shanghai Bell |
| R2-2304717 |
Session-less SL positioning and groupcast / broadcast messaging |
Nokia, Nokia Shanghai Bell |
| R2-2304770 |
Discussion on sidelink positioning |
CATT |
| R2-2304801 |
Discussion on Sidelink Positioning |
Huawei, HiSilicon |
| R2-2304949 |
UE Positioning using Sidelink |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2305066 |
SL PRS configuration |
Apple |
| R2-2305067 |
SL positioning groupcast and broadcast |
Apple |
| R2-2305068 |
[DARFT] Reply LS on SL positioning groupcast and broadcast |
Apple |
| R2-2305137 |
Further discussion on SLPP and session-based SL positioning |
Lenovo |
| R2-2305331 |
Discussion on sidelink positioning |
vivo |
| R2-2305343 |
Further discussion on sidelink positioning |
OPPO |
| R2-2305344 |
Further discussion on anchor UE reselection for sidelink positioning |
OPPO |
| R2-2305392 |
On SL Positioning Architecture Aspects |
Lenovo |
| R2-2305440 |
Further considerations on sidelink positioning |
Intel Corporation |
| R2-2305509 |
Considerations on sidelink positioning resources |
Sony |
| R2-2305562 |
Discussion on sidelink positioning |
Spreadtrum Communications |
| R2-2305636 |
Considerations on Sidelink positioning |
CMCC |
| R2-2305730 |
Draft Reply LS to SA3 on SL positioning groupcast and broadcast |
Xiaomi |
| R2-2305731 |
Discussion on SL positioning |
Xiaomi |
| R2-2305768 |
Discussion on Sidelink positioning |
InterDigital Inc. |
| R2-2305867 |
LMF roles and protocols for sidelink positioning |
MediaTek Inc. |
| R2-2306020 |
Sidelink positioning |
Ericsson |
| R2-2306078 |
Discussion on sidelink positioning |
ZTE Corporation |
| R2-2306145 |
SLPP design for session aspects |
Samsung R&D Institute UK |
| R2-2306334 |
SLPP session management and operation |
LG Electronics Inc. |
| R2-2306335 |
SLPP reliable transport functionality |
LG Electronics Inc. |
| R2-2306336 |
Sidelink positioning parameters for Anchor UE selection |
LG Electronics Inc. |
| R2-2306373 |
Discussion on Sidelink positioning parameters in discovery signalling |
Samsung |
| R2-2306422 |
Sidelink Positioning Protocol (SLPP) Signaling and Procedures |
Qualcomm Incorporated |
| R2-2306446 |
Further discussion on SL positioning procedures and signaling protocols for SL positioning |
CEWiT |
| R2-2306457 |
On the support of SL positioning server functionality |
Philips International B.V. |
| R2-2306515 |
On the selection of Anchor UEs for Sidelink Positioning |
Philips International B.V. |
| R2-2306671 |
Report of [AT122][401][POS] Sidelink positioning summary proposals (Xiaomi) |
Xiaomi |
| R2-2306696 |
Draft LS to SA2 on sidelink positioning agreements |
Intel |
| R2-2306757 |
[Pre122][401][POS] Summary of AI 7.2.2 on sidelink positioning |
Xiaomi |
| R2-2306842 |
LS to SA2 on sidelink positioning agreements |
RAN2 |
| 7.2.3 |
RAT-dependent integrity |
|
| R2-2304771 |
Discussion on RAT-dependent Integrity |
CATT |
| R2-2304800 |
Discussion on RAT-dependent Integrity |
Huawei, HiSilicon |
| R2-2305332 |
Signaling design of UE-based RAT-dependent integrity |
vivo |
| R2-2305341 |
Consideration on RAT-dependent positioning integrity |
OPPO |
| R2-2305441 |
Further considerations on RAT dependent integrity |
Intel Corporation |
| R2-2305563 |
Discussion on RAT-dependent integrity |
Spreadtrum Communications |
| R2-2305624 |
Discussion on the RAT-dependent integrity issues |
CMCC |
| R2-2305642 |
Discussion on RAT dependent integrity |
InterDigital, Inc. |
| R2-2305668 |
Discussion on RAT-dependent positioning integrity |
Xiaomi |
| R2-2305709 |
Discussion on RAT-dependent integrity |
Lenovo |
| R2-2305823 |
Integrity of NR Positioning Technologies |
Qualcomm Incorporated |
| R2-2306022 |
RAT Dependent positioning Integrity |
Ericsson |
| R2-2306076 |
Discussion on RAT-dependent methods positioning integrity |
ZTE Corporation |
| R2-2306255 |
LMF-based Integrity |
Nokia, Nokia Shanghai Bell |
| 7.2.4 |
LPHAP |
|
| R2-2304772 |
Discussion on LPHAP |
CATT |
| R2-2304799 |
Discussion on LPHAP |
Huawei, HiSilicon |
| R2-2304887 |
PRS and DRX configuration alignment |
Nokia, Nokia Shanghai Bell |
| R2-2304950 |
Enhancements for supporting LPHAP |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2305069 |
Alignment between DRX and PRS |
Apple |
| R2-2305333 |
Discussion on solution of LPHAP |
vivo |
| R2-2305342 |
Discussion on LPHAP |
OPPO |
| R2-2305442 |
Further considerations on LPHAP |
Intel Corporation |
| R2-2305510 |
Considerations on Low Power High Accuracy Positioning |
Sony |
| R2-2305564 |
Discussion on LPHAP |
Spreadtrum Communications |
| R2-2305637 |
Considerations on LPHAP |
CMCC |
| R2-2305644 |
Discussion on LPHAP |
InterDigital, Inc. |
| R2-2305669 |
Discussion on LPHA positioning |
Xiaomi |
| R2-2305710 |
Discussion on low power high accuracy positioning |
Lenovo |
| R2-2305822 |
Enhancements for LPHAP |
Qualcomm Incorporated |
| R2-2306021 |
Discussion on Low Power High Accuracy Positioning |
Ericsson |
| R2-2306075 |
Discussion on LPHAP |
ZTE Corporation |
| R2-2306447 |
Discussion on SRS configuration in RRC_INACTIVE |
Samsung |
| R2-2306540 |
Summary of AI 7.2.4: LPHAP |
Qualcomm Incorporated |
| R2-2306695 |
LS to SA2 on reporting positioning measurements taken in RRC_IDLE |
RAN2 |
| R2-2306700 |
Draft LS on LPHAP |
RAN2 |
| R2-2306841 |
LS on LPHAP |
RAN2 |
| 7.2.5 |
RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
|
| R2-2304773 |
Discussion on carrier phase positioning, bandwidth aggregation for positioning and Redcap positioning |
CATT |
| R2-2305315 |
Discussion on RAN1 led positioning topics |
Huawei, HiSilicon |
| R2-2305334 |
on-demand PRS for PRS bandwidth aggregation |
vivo |
| R2-2305443 |
Considerations on other RAN1 led items |
Intel Corporation |
| R2-2305625 |
Discussion on the RedCap UE positioning |
CMCC |
| R2-2305645 |
Discussion on positioning for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
InterDigital, Inc. |
| R2-2305670 |
Discussion on RedCap UE positioning |
Xiaomi |
| R2-2306023 |
RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
Ericsson |
| R2-2306077 |
Discussion on BW aggregation and RedCap positioning |
ZTE Corporation |
| R2-2306448 |
Discussion on bandwidth aggregation |
Samsung |
| 7.3.1 |
Organizational |
|
| R2-2304627 |
LS on the enhancements to restricting paging in a limited area (R3-232084; contact: Nokia) |
RAN3 |
| R2-2306067 |
Work plan for NR network energy savings |
Huawei, HiSilicon |
| R2-2306966 |
Running CR to 38300 for Network energy savings |
Ericsson |
| 7.3.2 |
DTX/DRX mechanism |
|
| R2-2304692 |
Discussion on Cell DTX/DRX configuration and operation |
Xiaomi |
| R2-2305013 |
Remaining issues for Cell DTX_DRX |
Samsung Electronics Co., Ltd |
| R2-2305081 |
Support high priority traffic in Cell DTX / DRX |
Apple, InterDigital, T-Mobile USA, MediaTek Inc., Intel |
| R2-2305082 |
Discussion on key open issues of Cell DTX / DRX |
Apple |
| R2-2305120 |
Cell DTX-DRX Mechanism |
Qualcomm Incorporated |
| R2-2305205 |
Discussion on Cell DTX/DRX |
Fujitsu |
| R2-2305321 |
Further discussion on cell DTX and DRX |
ZTE corporation, Sanechips |
| R2-2305335 |
Discussion on cell DTX-DRX mechanism |
vivo |
| R2-2305389 |
Discussion on cell DTX and DRX |
Huawei, HiSilicon |
| R2-2305435 |
Emergency calls, Voice, Scheduling Requests and RACH |
Vodafone |
| R2-2305529 |
Discussion on DTX/DRX mechanism |
OPPO |
| R2-2305628 |
Discussion on cell DTX/DRX |
CMCC |
| R2-2305651 |
Remaining issues on DTX/DRX |
Nokia, Nokia Shanghai Bell |
| R2-2305840 |
Further aspects on cell DTX/DRX |
Ericsson |
| R2-2305853 |
DL considerations for cell DTX/DRX |
NEC Telecom MODUS Ltd. |
| R2-2305855 |
UL considerations for Cell DTX/DRX |
NEC Telecom MODUS Ltd. |
| R2-2305870 |
Alignment between Cell DTX/DRX and C-DRX |
CATT, Turkcell |
| R2-2305925 |
Cell DTX/DRX mechanism |
InterDigital |
| R2-2305941 |
Various alignment aspects |
Lenovo |
| R2-2305975 |
Remaining issues for Cell DTX/DRX |
ETRI |
| R2-2306044 |
Discussion on DTX/DRX mechanism |
LG Electronics Inc. |
| R2-2306074 |
Considerations on Cell DTX/DRX |
KDDI Corporation |
| R2-2306222 |
Cell DTX/DRX NES Techniques |
III |
| R2-2306330 |
Discussion on SR transmission during the Cell DRX non-active period |
NTT DOCOMO INC. |
| R2-2306403 |
Discussion on cell DTX/DRX mechanisms - configuration and behaviour |
BT plc, KDDI |
| R2-2306407 |
Cell DTX and DRX Enhancements |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2306500 |
Reminding issues on stage 2 of the Cell DTX/DRX |
MediaTek Inc. |
| 7.3.3 |
SSB-less Scell operation |
|
| R2-2304694 |
Discussion on inter-band SSB-less Scell |
Xiaomi |
| R2-2304862 |
Enhancements of SBB/SIB-less NES solutions |
Dell Technologies |
| R2-2305083 |
Discussion on RAN2 work of inter-band SSB-less CA |
Apple |
| R2-2305250 |
Discussion on SSB/SIB-less Solutions for NES |
Samsung |
| R2-2305320 |
Discussion on SSB-less SCell operation for NES |
ZTE corporation, Sanechips |
| R2-2305336 |
RAN2 impact on supporting inter-band SSB-less Scell operation |
vivo |
| R2-2305721 |
Discuss on SSB-less SCell operation in NES |
Lenovo |
| R2-2305775 |
Discussion on SSB-less SCell operation |
CMCC |
| R2-2305841 |
SSB-less Scell operation on inter-band CA for FR1 |
Ericsson |
| R2-2305907 |
On NES SSB-less SCell operation |
Nokia, Nokia Shanghai Bell |
| R2-2305928 |
SSB-less Scell operation |
InterDigital |
| R2-2306068 |
Discussion on SSB-less SCell operation |
Huawei, HiSilicon |
| 7.3.4 |
Cell selection/re-selection |
|
| R2-2304691 |
Discussion on UE access control in NES cell |
Xiaomi |
| R2-2305121 |
Barring legacy UEs for NES Cells |
Qualcomm Incorporated, T-Mobile US |
| R2-2305251 |
Discussion on Cell Selection and Reselection for NES |
Samsung |
| R2-2305323 |
Consideration on preventing legacy UEs camping on NES cell |
ZTE corporation, Sanechips |
| R2-2305337 |
Discussion on cell selection/re-selection |
vivo |
| R2-2305390 |
Discussion on cell selection/reselection for NES |
Huawei, HiSilicon |
| R2-2305455 |
Definition of NES and barring on cell DTX/DRX cells |
Vodafone |
| R2-2305530 |
Discussion on cell selection reselection |
OPPO |
| R2-2305718 |
Cell selection/re-selection in NES |
Lenovo |
| R2-2305776 |
Discussion on cell barring and reselection for NES |
CMCC |
| R2-2305842 |
NES Cell selection/reselection |
Ericsson |
| R2-2305858 |
Procedure for legacy UEs camping on NES cells |
NEC Telecom MODUS Ltd. |
| R2-2305871 |
Consideration on Cell Selection/Re-selection on NES cells |
CATT, Turkcell |
| R2-2305892 |
Cell Reselection Enhancements Supporting NES |
Google Inc. |
| R2-2305926 |
Cell selection and resection for NES |
InterDigital |
| R2-2305974 |
Legacy UE Handling for NES |
ETRI |
| R2-2306059 |
Considerations on Cell selection/re-selection |
KDDI Corporation |
| R2-2306276 |
Access control enhancement for NES |
LG Electronics France |
| R2-2306329 |
Discussion on Cell selection |
NTT DOCOMO INC. |
| R2-2306361 |
Reselection and Paging handling for NES |
Nokia, Nokia Shanghai Bell |
| R2-2306406 |
Identify NES capable UEs by network |
BT plc |
| R2-2306410 |
Cell Selection and Re-Selection for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2306538 |
Access control enhancement for NES |
LG Electronics France |
| 7.3.5 |
Connected mode mobility |
|
| R2-2304693 |
Discussion on UE mobility due to NES cell |
Xiaomi |
| R2-2305084 |
Discussion on CHO enhancement in NES |
Apple |
| R2-2305122 |
NES Connected mode mobility |
Qualcomm Incorporated |
| R2-2305206 |
Discussion on Connected mode mobility for network energy savings |
Fujitsu |
| R2-2305252 |
Discussion on Connected mode mobility for NES |
Samsung |
| R2-2305322 |
Further discussion on connected mode mobility |
ZTE corporation, Sanechips |
| R2-2305338 |
Conditional handover enhancement for network energy saving |
vivo |
| R2-2305461 |
Triggering conditions and other aspects of the Handover to/from DTX/DRX cells |
Vodafone GmbH |
| R2-2305511 |
Handover enhancement for NES |
Sony |
| R2-2305531 |
Discussion on connected mode mobility |
OPPO |
| R2-2305629 |
Discussion on Connected mode mobility |
CMCC |
| R2-2305860 |
CHO for NES |
Ericsson |
| R2-2305864 |
CHO procedure enhancement to support NES mode |
NEC Telecom MODUS Ltd. |
| R2-2305872 |
CHO enhancement for NES |
CATT, Turkcell |
| R2-2305890 |
CHO Enhancements Supporting NES |
Google Inc. |
| R2-2305927 |
NES mobility aspects |
InterDigital |
| R2-2305942 |
CHO Procedure in NES Mode |
Lenovo |
| R2-2306052 |
Discussion on CHO enhancements for NES |
Sharp |
| R2-2306069 |
Discussion on CHO enhancement for NES |
Huawei, HiSilicon |
| R2-2306240 |
Mobility enhancement: mobility triggering by light handover command |
LG Electronics Inc. |
| R2-2306362 |
CHO on NES |
Nokia, Nokia Shanghai Bell |
| 7.3.6 |
Others |
|
| R2-2305123 |
Discussion of RAN3 LS on Restricting Paging |
Qualcomm Incorporated |
| R2-2305512 |
Skip monitoring of CSI-RS during non-active periods |
Sony |
| 7.4.1 |
Organizational |
|
| R2-2304620 |
LS on beam indication of target cell(s) and time gap between a PDCCH order and the corresponding PRACH transmission for LTM (R1-2304276; contact: Fujitsu, MediaTek, CATT) |
RAN1 |
| R2-2304629 |
Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM (R3-232139; contact: Fujitsu, CATT) |
RAN3 |
| R2-2304784 |
37.340 running CR for introduction of NR further mobility enhancements |
ZTE Corporation, Sanechips |
| R2-2304928 |
38_331_Running CR for CHO including target MCG and candidate SCGs |
CATT |
| R2-2305296 |
RRC running CR for selective activation of SCGs for NR-DC |
OPPO |
| R2-2305303 |
38.300 running CR for introduction of NR further mobility enhancements |
MediaTek Inc., vivo |
| R2-2305539 |
38.321 running CR for introduction of NR further mobility enhancements |
Huawei, HiSilicon |
| R2-2306014 |
RRC open issues list for LTM |
Ericsson |
| R2-2306015 |
RRC running CR for LTM |
Ericsson |
| R2-2306924 |
38.321 running CR for introduction of NR further mobility enhancements |
Huawei, HiSilicon |
| R2-2306952 |
37.340 running CR for introduction of NR further mobility enhancements |
ZTE Corporation, Sanechips |
| R2-2306957 |
38.300 running CR for introduction of NR further mobility enhancements |
MediaTek Inc., vivo |
| 7.4.2 |
L1L2 Triggered Mobility |
|
| R2-2304944 |
Delayed Resource Reservation for inter gNB-DU L1/L2 Triggered Mobility |
Rakuten Symphony |
| R2-2304963 |
TA Acquisition before LTM Serving cell change |
Rakuten Symphony |
| R2-2304964 |
Prioritizing RACH-less LTM HO |
Rakuten Symphony |
| R2-2304966 |
Security impacts of intra gNB, inter gNB-CU-UP relocation |
Rakuten Symphony |
| 7.4.2.1 |
General and Stage-2 |
|
| R2-2304673 |
L1 Measurement to support LTM |
NEC |
| R2-2304674 |
Failure handling for L1/L2 triggered mobility |
NEC |
| R2-2304675 |
UE identification during RACH less LTM cell switch |
NEC |
| R2-2304687 |
Discussion on RACH-less LTM |
CATT |
| R2-2304719 |
RAN2 Aspects of Early Timing Advance Management for LTM |
Samsung Electronics Co., Ltd |
| R2-2304881 |
On unified sequential LTM with flexible cell switch triggering and RACH-less |
Futurewei |
| R2-2304889 |
Open Issues for LTM Procedure |
MediaTek Inc. |
| R2-2304909 |
Remaining issues on LTM procedures |
vivo |
| R2-2304910 |
Remaining issues on early TA acquisition |
vivo |
| R2-2304951 |
General aspects for L1/L2 triggered mobility procedure |
Fujitsu |
| R2-2305101 |
LTM cell switch link failure handling |
Apple |
| R2-2305104 |
RACH-less LTM and TA management |
Apple |
| R2-2305116 |
Discussion on LTM procedures |
Qualcomm Inc. |
| R2-2305164 |
LTM Stage 2 open issues |
Interdigital, Inc. |
| R2-2305165 |
LTM Measurement considerations |
Interdigital, Inc. |
| R2-2305271 |
Remaining issues of LTM general |
LG Electronics |
| R2-2305292 |
Discussion on early TA acquisition and maintenance for LTM |
OPPO |
| R2-2305293 |
Open issues for RACH-less LTM |
OPPO |
| R2-2305305 |
Data Loss at LTM Cell Switch |
MediaTek Inc. |
| R2-2305316 |
On LTM performance, candidate SCell and failure handling aspect |
CATT |
| R2-2305365 |
Discussion on LTM supervisor timer |
FGI |
| R2-2305368 |
Discussion on early TA acquisition for LTM |
Transsion Holdings |
| R2-2305459 |
Discussion on early TA acquisition for LTM |
ITRI |
| R2-2305540 |
RACH-less LTM and LTM procedure |
Huawei, HiSilicon |
| R2-2305575 |
Discussion on RACH-less LTM |
Xiaomi |
| R2-2305638 |
Considerations on failure handling |
CMCC |
| R2-2305639 |
Discussions on LTM open issues |
CMCC |
| R2-2305640 |
Remaining issues related to measurements |
CMCC |
| R2-2305879 |
Further details on TA Acquisition and Maintenance in LTM |
Nokia, Nokia Shanghai Bell |
| R2-2305944 |
Initial Early-TA acquisition |
Lenovo |
| R2-2306011 |
Discussion on TA handling aspects for LTM |
Ericsson |
| R2-2306016 |
Signalling approaches for LTM cell switch execution |
Ericsson |
| R2-2306051 |
Failure detection and fast recovery |
Fujitsu |
| R2-2306281 |
Discussion on RACH related issue |
NTT DOCOMO INC. |
| R2-2306316 |
Discussion on early TA acquisition and partial MAC reset |
LG Electronics Inc. |
| R2-2306419 |
Further Considerations on Early RACH for LTM |
ZTE Corporation, Sanechips |
| R2-2306428 |
Discussion on TA timer for LTM |
KDDI Corporation |
| R2-2306479 |
Discussion on LTM command MAC CE content and RAN3 LS reply |
China Unicom |
| R2-2306480 |
Discussion on RACH-less LTM and early acquisition of TA |
China Unicom |
| R2-2306875 |
LS on Early TA and RACH-less |
Ericsson |
| R2-2306897 |
LS on Early TA and RACH-less |
RAN2 |
| 7.4.2.2 |
RRC |
|
| R2-2304785 |
Discussion on RRC aspects for LTM |
ZTE Corporation, Sanechips |
| R2-2304882 |
Configuration for measurement and RACH-less in sequential LTM |
Futurewei |
| R2-2304890 |
Open Issues for LTM RRC |
MediaTek Inc. |
| R2-2304911 |
RRC configuration for LTM |
vivo |
| R2-2304952 |
RRC aspects of L1/L2 triggered mobility |
Fujitsu |
| R2-2305024 |
Remaining issues on L1 measurement configuration for LTM |
Panasonic |
| R2-2305100 |
RRC based L2 reset config |
Apple |
| R2-2305103 |
On Validation of LTM candidate config |
Apple |
| R2-2305117 |
RRC Aspects of LTM |
Qualcomm Inc. |
| R2-2305118 |
Race conditions in LTM |
Qualcomm Inc. |
| R2-2305166 |
RRC Open issues for LTM |
Interdigital, Inc. |
| R2-2305272 |
Discussion on L1 measurement configuration |
LG Electronics |
| R2-2305294 |
Discussion on reference configuration and candidate configuration for LTM |
OPPO |
| R2-2305317 |
Discussion on RRC aspects for LTM |
CATT |
| R2-2305369 |
Discussion on measurement configuration for LTM |
Transsion Holdings |
| R2-2305537 |
Discussion on L1 measurement for LTM |
ZTE Corporation, Sanechips |
| R2-2305559 |
Discussion on the remaining issues for LTM |
Spreadtrum Communications |
| R2-2305574 |
Remaining issues of RRC configured Layer-2 reset |
Xiaomi |
| R2-2305594 |
Discussion on RRC aspects for LTM |
Samsung R&D Institute India |
| R2-2305648 |
Discussion on RAN3 related issues |
NEC |
| R2-2305695 |
Compliance check for LTM configuration |
Lenovo |
| R2-2305880 |
On Reference, Delta and Validity Check for LTM Configuration |
Nokia, Nokia Shanghai Bell |
| R2-2305908 |
Discussion on RRC Reconfiguration Aspects |
Nokia, Nokia Shanghai Bell |
| R2-2305918 |
RRC aspects for LTM |
Huawei, HiSilicon |
| R2-2306010 |
Discussion on RRC aspects for LTM |
Ericsson |
| R2-2306012 |
L1 measurements aspects for LTM |
Ericsson |
| R2-2306132 |
Discussion on RRC aspects for LTM |
Xiaomi |
| R2-2306279 |
Candidate configuration handling for LTM |
LG Electronics France |
| R2-2306319 |
Remaining issues for RRC Configurations of LTM |
Sharp |
| R2-2306423 |
Discussion on LTM reference configuration |
Google Inc. |
| R2-2306769 |
Summary of [AT122][005][Mob18] LTM L1 measurement aspects |
Ericsson |
| R2-2306873 |
LS on L1 measurements for LTM |
Ericsson |
| R2-2306898 |
LS on L1 measurements for LTM |
RAN2 |
| 7.4.2.3 |
Cell Switch |
|
| R2-2304688 |
Discussions on Cell Switch |
CATT |
| R2-2304720 |
Remaining issues for Cell Switching |
Samsung Electronics Co., Ltd |
| R2-2304883 |
Discussion on issues at lower layer mobility with RACH-less |
Futurewei |
| R2-2304891 |
Triggering MAC CE for LTM |
MediaTek Inc. |
| R2-2304912 |
Remaining issues on partial MAC reset |
vivo, MediaTek Inc., Samsung |
| R2-2304953 |
Discussions on LTM cell switch execution |
Fujitsu |
| R2-2305119 |
Dynamic switch in LTM |
Qualcomm Inc. |
| R2-2305167 |
LTM MAC CE content and functionality |
Interdigital, Inc. |
| R2-2305295 |
Discussion on MAC CE content and partial MAC reset for LTM |
OPPO |
| R2-2305370 |
Discussion on remaining issue for LTM |
Transsion Holdings |
| R2-2305541 |
LTM command MAC CE content and RAN3 LS reply |
Huawei, HiSilicon, CATT, ZTE Corporation, Sanechips, vivo, China Unicom |
| R2-2305576 |
Contents of cell switch MAC CE |
Xiaomi |
| R2-2305641 |
Further considerations on cell switch |
CMCC |
| R2-2305643 |
Discussion on partial MAC reset for LTM |
KDDI Corporation |
| R2-2305649 |
Further discussion on cell switch |
NEC |
| R2-2305909 |
On the cell switch in LTM |
Nokia, Nokia Shanghai Bell |
| R2-2305919 |
L2 behaviours and reset indication |
Huawei, HiSilicon |
| R2-2305943 |
Cell Switch details |
Lenovo |
| R2-2306013 |
LTM cell switch command and UE actions |
Ericsson |
| R2-2306120 |
Discussion on fallback RACH for L1L2-triggered mobility |
ASUSTeK |
| R2-2306226 |
Beam handling and security issue on cell switch for LTM |
Samsung |
| R2-2306371 |
Cell Switch for LTM |
Sharp |
| R2-2306405 |
Securing LTM |
Lenovo |
| R2-2306418 |
Further Considerations On MAC Partial Reset |
ZTE Corporation, Sanechips |
| R2-2306775 |
Report of [AT122][006][Mob18] Partial MAC reset (vivo) |
vivo |
| 7.4.3 |
NR-DC with selective activation cell of groups |
|
| R2-2304689 |
Discussion on Selective Activation of Cell Groups in NR-DC |
CATT |
| R2-2304786 |
Consideration on SCG selective activation |
ZTE Corporation, Sanechips |
| R2-2304913 |
Remaining issues for NR-DC with selective activation cell of groups |
vivo |
| R2-2305105 |
Execution condition in selective SCG activation |
Apple |
| R2-2305214 |
SCG Selective Activation in NR-DC |
Qualcomm Incorporated |
| R2-2305297 |
Open issues for selective activation of SCGs for NR-DC |
OPPO |
| R2-2305366 |
Discussion on NR-DC with Selective Activation of Cell Groups |
FGI |
| R2-2305371 |
Discussion on Selective Activation of Cell Groups in NR-DC |
Transsion Holdings |
| R2-2305385 |
NR-DC with selective activation |
Ericsson |
| R2-2305555 |
Discussion on NR-DC with SCG selective activation |
Spreadtrum Communications |
| R2-2305608 |
Discussion on NR-DC with selective activation of cell groups |
CMCC |
| R2-2305650 |
Configurations for selective SCG activation |
NEC |
| R2-2305679 |
Discussion on issues related to SCG selective activation |
Lenovo |
| R2-2305812 |
Subsequent change of SCGs and selective activation |
Interdigital Inc. |
| R2-2305861 |
On remaining issues of selective activation |
Nokia, Nokia Shanghai Bell |
| R2-2305920 |
NR-DC with selective SCG activatiion |
Huawei, HiSilicon |
| R2-2306105 |
Discussion on NR-DC with selective activation cell of groups |
KDDI Corporation |
| R2-2306133 |
Discussion on NR-DC with SCG selective activation |
Xiaomi |
| R2-2306227 |
Considerations on Subsequent CPAC after SCG Change |
Samsung |
| R2-2306274 |
Further discussion on execution condition related issue |
NTT DOCOMO INC. |
| R2-2306309 |
Discussion on selective SCG activation |
MediaTek Inc. |
| R2-2306372 |
Remaining issues for SCG selective activation |
Sharp |
| R2-2306376 |
Discussion on NR-DC with selective activation of the cell groups. |
DENSO CORPORATION |
| R2-2306429 |
Selective CG Activation in NR |
LG Electronics |
| 7.4.4 |
CHO including target MCG and candidate SCGs for CPC CPA in NR-DC |
|
| R2-2304690 |
Discussion on CHO including target MCG and candidate SCGs |
CATT |
| R2-2304787 |
Discussion on CHO with candidate SCGs |
ZTE Corporation, Sanechips |
| R2-2304914 |
Discussion on CHO with CPAC |
vivo |
| R2-2305010 |
Considerations on CHO with CPA/CPC |
Samsung |
| R2-2305102 |
Using SCG deactived state for CHO with SN addition |
Apple |
| R2-2305213 |
CHO with multiple candidate SCGs |
Qualcomm Incorporated |
| R2-2305239 |
Discussion on evaluation and execution of CHO with CPAC in NR-DC |
China Telecom |
| R2-2305298 |
Discussion on configuration, evaluation and execution for CHO with CPA/CPC |
OPPO |
| R2-2305386 |
CHO with associated CPC or CPA |
Ericsson |
| R2-2305542 |
CHO including target MCG and candidate SCGs for CPC/CPA |
Huawei, HiSilicon |
| R2-2305556 |
Discussion on CHO with CPAC in NR-DC |
Spreadtrum Communications |
| R2-2305630 |
Discussion CHO including target MCG and candidate SCGs for CPAC |
CMCC |
| R2-2305696 |
CHO with candidate SCG for CPAC |
Lenovo |
| R2-2305813 |
CHO with associated SCG |
Interdigital Inc. |
| R2-2305881 |
Further details on CHO with CPAC in Rel-18 |
Nokia, Nokia Shanghai Bell |
| R2-2306134 |
Discussion on CHO with CPAC |
Xiaomi |
| R2-2306297 |
Discussion on CHO with candidate SCG |
MediaTek Inc. |
| R2-2306430 |
Simultaneous Evaluation for CHO and CPAC |
LG Electronics |
| 7.5.1 |
Organizational |
|
| R2-2304659 |
LS out on the N6 PDU Set Identification (S4-230739; contact: Intel) |
SA4 |
| R2-2305186 |
Work Plan for Rel-18 WI on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs); Ericsson (RAN1 FL) |
| R2-2305187 |
SA2 Status for XR |
Nokia, Qualcomm (Rapporteurs) |
| R2-2305188 |
SA4 Status for XR |
Nokia, Qualcomm (Rapporteurs) |
| R2-2305189 |
Stage 2 Overview of XR Enhancements |
Nokia, Qualcomm (Rapporteurs) |
| R2-2305492 |
UE Capabilities for Rel-18 XR WI |
Intel Corporation |
| R2-2306920 |
XR Enhancements |
Nokia, Qualcomm (Rapporteurs) |
| 7.5.2 |
XR awareness |
|
| R2-2304708 |
Discussion on XR awareness |
Qualcomm Incorporated |
| R2-2304865 |
Further discussions on XR awareness |
Futurewei |
| R2-2304915 |
Discussion on XR awareness |
vivo |
| R2-2304967 |
Enhancements for XR awareness |
CATT, Dell Technologies |
| R2-2305005 |
Discussion on XR awareness |
Xiaomi Communications |
| R2-2305016 |
XR Awareness in RAN |
ZTE Corporation, Sanechips |
| R2-2305071 |
Views on XR-Awareness |
Apple |
| R2-2305158 |
XR awareness |
InterDigital |
| R2-2305190 |
Jitter and End of Data Burst Signalling |
Nokia, Nokia Shanghai Bell |
| R2-2305301 |
Discussion on periodicity, jitter, and end of burst indication |
KDDI Corporation |
| R2-2305361 |
XR awareness |
NEC |
| R2-2305493 |
XR Awareness in UE and RAN |
Intel Corporation |
| R2-2305513 |
Considerations on XR PDU prioritization |
Sony |
| R2-2305532 |
Discussion on XR awareness |
OPPO |
| R2-2305536 |
On XR awareness |
Google Inc. |
| R2-2305565 |
Discussion on XR awareness |
Spreadtrum Communications |
| R2-2305634 |
Remaining Issues on UL Traffic assistance information for XR |
CMCC |
| R2-2305684 |
Discussion on PDU sets and data burst awareness in RAN |
Lenovo |
| R2-2305740 |
Discussion on UL jitter information |
Samsung |
| R2-2305808 |
Discussion on PDU set and data burst information |
Huawei, HiSilicon |
| R2-2305827 |
Discussion on XR-awareness |
Ericsson |
| R2-2305897 |
RAN awareness of XR characteristics |
MediaTek Inc. |
| R2-2306205 |
Further discussion on XR awareness |
TCL Communication |
| R2-2306333 |
Discussion on XR awareness |
LG Electronics Inc. |
| R2-2306463 |
Discussion on XR-awareness |
NTT DOCOMO, INC. |
| R2-2306481 |
Discussion on XR awareness |
China Unicom |
| R2-2306568 |
LS response to N6 PDU Set Identification |
RAN2 |
| R2-2306572 |
LS response to N6 PDU Set Identification |
RAN2 |
| 7.5.3 |
XR-specific power saving |
|
| R2-2304709 |
Discussion on DRX mismatch problem for XR |
Qualcomm Incorporated, MediaTek, CATT, vivo, NEC, Meta |
| R2-2304710 |
Discussion on SFN wrap around problem for XR |
Qualcomm Incorporated, Huawei, HiSilicon, Meta |
| R2-2304808 |
Discussion on C-DRX enhancements for XR |
Huawei, HiSilicon |
| R2-2304916 |
Analysis on introducing H-SFN for DRX formulas |
vivo |
| R2-2304954 |
Discussions on DRX enhancements for XR |
Fujitsu |
| R2-2304968 |
Enhancements for SFN wrap-around |
CATT |
| R2-2305006 |
Discussing on XR-specific C-DRX enhancement |
Xiaomi Communications |
| R2-2305007 |
Discussion on power saving scheme for XR |
Samsung |
| R2-2305017 |
XR-specific power saving |
ZTE Corporation, Sanechips |
| R2-2305072 |
C-DRX enhancements for XR |
Apple |
| R2-2305159 |
XR-specific power saving |
InterDigital |
| R2-2305367 |
Discussion on DRX enhancements for XR |
FGI |
| R2-2305456 |
Discussion on C-DRX enhancement for XR |
NEC Corporation |
| R2-2305458 |
Discussion on DRX cycle alignment for XR |
ITRI |
| R2-2305494 |
C-DRX Enhancements for XR Traffic |
Intel Corporation |
| R2-2305543 |
XR-specific power saving enhancement |
Google Inc. |
| R2-2305593 |
Discussion on power saving aspects for XR |
Continental Automotive |
| R2-2305626 |
Discussion on the DRX enhancement |
CMCC |
| R2-2305652 |
DRX enhancements for XR |
Nokia, Nokia Shanghai Bell, Continental Automotive |
| R2-2305685 |
Discussion of DRX enhancement |
Lenovo |
| R2-2305830 |
Discussion on XR-specific power saving |
Ericsson |
| R2-2305898 |
Considerations for SFN wrap around solution |
MediaTek Inc., LGE |
| R2-2306143 |
DRX enhancement for power saving in XR |
LG Electronics Inc. |
| R2-2306203 |
Discussion on various frame rates supported for XR-specific power |
III |
| R2-2306564 |
LS on new DRX cycles in rational numbers |
RAN2 |
| 7.5.4.1 |
BSR enhancements for XR |
|
| R2-2304711 |
BSR and delay status report for XR |
Qualcomm Incorporated |
| R2-2304826 |
Discussion on BSR and DSR for XR |
TCL Communication Ltd. |
| R2-2304861 |
BSR Enhancements For XR |
Dell Technologies |
| R2-2304864 |
Further discussions on BSR enhancements for XR |
Futurewei |
| R2-2304917 |
Discussion on BSR enhancements for XR |
vivo |
| R2-2304955 |
Discussions on delay information reporting |
Fujitsu |
| R2-2304969 |
On BSR Enhancements |
CATT |
| R2-2305002 |
Discussing on BSR enhancements for XR capacity |
Xiaomi Communications |
| R2-2305018 |
BSR enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2305073 |
Views on BSR Enhancements for XR |
Apple |
| R2-2305149 |
New BS table(s) and BSR trigger(s) |
NEC |
| R2-2305364 |
Generate new buffer status report table |
FGI |
| R2-2305388 |
Discussion on BSR enhancements for XR |
Honor |
| R2-2305454 |
Discussion on BSR enhancement for delay information report |
NEC Corporation |
| R2-2305495 |
BSR Enhancements for XR Traffic |
Intel Corporation |
| R2-2305514 |
Considerations on XR UL PDU set information |
Sony |
| R2-2305515 |
Some considerations on BSR enhancements for XR |
Sony |
| R2-2305533 |
Discussion on BSR enhancement for XR |
OPPO |
| R2-2305571 |
Consideration on BSR enhancements for XR |
Spreadtrum Communications |
| R2-2305604 |
Consideration on Piecewise Linear BS Table |
CMCC, Huawei, HiSilicon, China Unicom |
| R2-2305653 |
BSR enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2305723 |
Discussion on BSR enhancements for XR |
Lenovo |
| R2-2305816 |
BSR enhancements for XR |
Interdigital Inc. |
| R2-2305828 |
Discussion on BSR enhancements for XR |
Ericsson |
| R2-2306130 |
Discussion on MAC enhancements for XR-specific capacity improvement |
Huawei, HiSilicon |
| R2-2306176 |
BSR enhancements for XR |
MediaTek Inc. |
| R2-2306242 |
Discussion on delay information for XR |
Google Inc. |
| R2-2306243 |
Discussion on BSR enhancements for XR |
Google Inc. |
| R2-2306252 |
Discussion on residual resource allocation for XR |
Google Inc. |
| R2-2306275 |
Discussion on BSR enhancements for XR |
III |
| R2-2306346 |
Discussion on new BSR table and delay information report |
LG Electronics Inc. |
| R2-2306353 |
Discussion on BSR enhancements for XR |
Samsung |
| R2-2306393 |
XR BSR and Delay Information Enhancements |
Meta USA |
| 7.5.4.2 |
Discard operation for XR |
|
| R2-2304712 |
Discussion on discard operation |
Qualcomm Incorporated |
| R2-2304827 |
Discussion on discard indication for XR |
TCL Communication Ltd. |
| R2-2304918 |
Discussion on discard operation for XR |
vivo |
| R2-2304956 |
Discussions on PDU discard based on PDU Set Importance |
Fujitsu |
| R2-2304970 |
Discard Operation for XR |
CATT |
| R2-2305001 |
Discussing on PDU discarding of XR traffic |
Xiaomi Communications |
| R2-2305012 |
PDU discard |
CANON Research Centre France |
| R2-2305019 |
PDU discard for XR |
ZTE Corporation, Sanechips |
| R2-2305074 |
Views on PDU Discard Operation for XR |
Apple |
| R2-2305150 |
PDU discard |
NEC |
| R2-2305160 |
Discard operation for XR |
InterDigital |
| R2-2305191 |
Discard operation for XR |
Nokia, Nokia Shanghai Bell |
| R2-2305457 |
Discussion on the issues of PDU-Set discard |
ITRI |
| R2-2305496 |
Discard Enhancements for XR Traffic |
Intel Corporation |
| R2-2305534 |
Discussion on discard operation for XR |
OPPO |
| R2-2305566 |
Discussion on XR discard |
Spreadtrum Communications |
| R2-2305635 |
PDU-Set Discard operation for XR |
CMCC |
| R2-2305724 |
Discard operation for XR communications |
Lenovo |
| R2-2305784 |
Discard Operation for XR |
Samsung R&D Institute India |
| R2-2305829 |
Discussion on PDU Discard |
Ericsson |
| R2-2305899 |
Further aspects of PDU discard |
MediaTek Inc. |
| R2-2306106 |
Further discussions on discard operation for XR |
Futurewei |
| R2-2306121 |
Discussion on PDU Set discard in PDCP layer for DL and UL |
ASUSTeK |
| R2-2306137 |
Discussion on PDU set discarding for XR traffic |
Huawei, HiSilicon |
| R2-2306331 |
Discussion on the discard for XR |
LG Electronics Inc. |
| R2-2306402 |
Discussion on PDU Discard Operation for XR |
Meta USA |
| R2-2306565 |
Offline 204 on XR Discard |
Nokia (Rapporteur) |
| 7.5.4.3 |
Configured Grant enhancements for XR |
|
| R2-2304713 |
Configured grant enhancements for XR |
Qualcomm Incorporated |
| R2-2304809 |
Discussion on retransmission-less CG for XR |
Huawei, Apple, Futurewei, Google, HiSilicon, Intel, Lenovo, MediaTek, Meta, Qualcomm |
| R2-2304919 |
Discussion on CG enhancements for XR |
vivo |
| R2-2304971 |
Enhancements for configured grant |
CATT |
| R2-2305020 |
Configured Grant enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2305075 |
Views on Configured Grant Enhancements for XR |
Apple |
| R2-2305161 |
Configured Grant enhancements for XR |
InterDigital |
| R2-2305516 |
Configured Grant enhancements for XR |
Sony |
| R2-2305517 |
Options for Retransmission-less CG for XR traffic |
Sony |
| R2-2305535 |
Discussion on configured grant enhancement for XR |
OPPO |
| R2-2305538 |
On Configured Grant enhancements for XR |
Google Inc. |
| R2-2305605 |
Consideration on Retransmission less CG on XR |
CMCC |
| R2-2305654 |
Retransmission-less operation |
Nokia, Nokia Shanghai Bell |
| R2-2305725 |
Details of CG enhancements for XR communications |
Lenovo |
| R2-2305741 |
Discussion on retransmission-less CG |
Samsung |
| R2-2306185 |
HARQ ID determination formula for CG |
MediaTek Inc. |
| R2-2306206 |
Discussion on multiple-PUSCHs CG for XR |
TCL Communication |
| R2-2306266 |
Configured Grant enhancements for XR |
Ericsson |
| R2-2306272 |
Discussion on Configured Grant enhancements for XR |
III |
| R2-2306347 |
Discussion on CG enhancement for XR |
LG Electronics Inc. |
| 7.6.1 |
Organizational |
|
| R2-2304612 |
LS on GNSS position fix during inactive state of Connected DRX for improved GNSS operations (R1-2304126; contact: MediaTek) |
RAN1 |
| R2-2304737 |
36.321 (MAC) Running CR for IoT-NTN |
Mediatek Inc. |
| R2-2305199 |
Running CR for TS 36.306 for Rel-18 IoT NTN |
Qualcomm Incorporated |
| R2-2306065 |
36331 running CR for IOT NTN |
Huawei, HiSilicon |
| R2-2306265 |
Running CR for R18 IoT NTN |
Ericsson |
| R2-2306951 |
Running CR for R18 IoT NTN |
Ericsson |
| R2-2306954 |
36331 running CR for IOT NTN |
Huawei, HiSilicon |
| R2-2306956 |
Running CR for TS 36.306 for Rel-18 IoT NTN |
Qualcomm Incorporated |
| R2-2306959 |
Running CR for TS 36.304 for Rel-18 IoT-NTN |
Nokia |
| R2-2306962 |
Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN |
Mediatek Inc. |
| 7.6.2 |
Performance Enhancements |
|
| R2-2306485 |
On improved GNSS operation for IoT NTN |
Samsung Suzhou |
| 7.6.2.1 |
HARQ enhancements |
|
| R2-2304731 |
On Disabling HARQ Feedback in IoT-NTN |
Mediatek Inc. |
| R2-2304740 |
Discussion on HARQ enhancement for IoT NTN |
OPPO |
| R2-2304813 |
Discussion on HARQ mode for PUR |
Huawei, Turkcell, HiSilicon |
| R2-2304893 |
Discussion on the HARQ enhancements in IoT NTN |
CATT |
| R2-2305168 |
Remaining Issues on Disabling HARQ feedback for IoT-NTN |
Interdigital, Inc. |
| R2-2305200 |
UL HARQ process enhancement |
Qualcomm Incorporated |
| R2-2305609 |
Discussion on the HARQ enhancement for IoT-NTN |
CMCC |
| R2-2305727 |
Discussion on HARQ enhancement |
Xiaomi |
| R2-2305758 |
On HARQ enhancements for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2305956 |
Further discussion on HARQ enhancements |
ZTE Corporation, Sanechips |
| R2-2306264 |
R18 IoT NTN HARQ enhancements |
Ericsson |
| 7.6.2.2 |
GNSS operation enhancements |
|
| R2-2304732 |
GNSS Operation Enhancements in IoT-NTN |
MediaTek Inc. |
| R2-2304751 |
Discussion on GNSS operation for IoT NTN |
OPPO |
| R2-2304814 |
Discussion on GNSS operation enhancements |
Huawei, Turkcell, HiSilicon |
| R2-2304894 |
Discussion on GNSS operation in connected mode |
CATT |
| R2-2305151 |
GNSS fix in connected mode |
NEC |
| R2-2305169 |
GNSS acquisition and reporting for IoT NTN |
Interdigital, Inc. |
| R2-2305203 |
GNSS fix in RRC_CONNECTED |
Qualcomm Incorporated |
| R2-2305610 |
Discussion on GNSS enhancement for IoT-NTN |
CMCC |
| R2-2305711 |
Further considerations on GNSS operations in RRC_CONNECTED for IoT NTN |
Lenovo |
| R2-2305726 |
Discussion on GNSS operation enhancement |
Xiaomi |
| R2-2305759 |
GNSS operation enhancements for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2305894 |
Issues for the GNSS Validity Reporting |
Google Inc. |
| R2-2305957 |
Further discussion on GNSS reacquisition |
ZTE Corporation, Sanechips |
| R2-2305992 |
GNSS operation enhancements |
SHARP Corporation |
| R2-2306166 |
Improved GNSS Operation |
Apple |
| R2-2306263 |
R18 IoT NTN GNSS operation enhancements |
Ericsson |
| R2-2306641 |
Summary of [AT122][101][IoT NTN] GNSS operation enhancements (Apple) |
Apple |
| 7.6.3.1 |
Enhancements for neighbour cell measurements |
|
| R2-2304733 |
On Enhancing Neighbor Cell Measurements in IoT-NTN |
MediaTek Inc. |
| R2-2304741 |
Discussion on measurement triggering enhancement for IoT NTN |
OPPO |
| R2-2304742 |
Discussion on neighbour cell assistance information for IoT NTN |
OPPO |
| R2-2304895 |
Discussion on the mobility enhancements for IoT NTN UE |
CATT |
| R2-2305170 |
Neighbour cell measurements before RLF and CHO enhancements |
Interdigital, Inc. |
| R2-2305202 |
Satellite and coverage information signalling |
Qualcomm Incorporated |
| R2-2305611 |
Discussion on mobility enhancements for IoT-NTN |
CMCC |
| R2-2305671 |
Discussion on the neighbour cell measurement for RRC Connected UE |
Xiaomi |
| R2-2305712 |
On location-based neighbour cell measurement in RRC_CONNECTED in IoT NTN |
Lenovo |
| R2-2305862 |
Further analysis on mobility enhancements for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2305958 |
Further discussion on neighbor satellite assistance information and new triggers for neighbor cell measurement |
ZTE Corporation, Sanechips |
| R2-2306066 |
Enhancements for neighbour cell measurements |
Huawei, HiSilicon, Turkcell |
| R2-2306168 |
Neighbour cell measurements before RLF for NB-IoT |
Apple |
| R2-2306254 |
Neighbour cell measurements before RLF |
Ericsson |
| R2-2306484 |
On enhancements for neighbour cell measurements |
Samsung Suzhou |
| R2-2306642 |
[offline-102] Mobility enhancements |
Qualcomm Incorporated |
| R2-2306664 |
[offline-102] Mobility enhancements – second round |
Qualcomm |
| R2-2306665 |
[offline-113] Measurements before RLF |
InterDigital |
| 7.6.3.2 |
Other |
|
| R2-2305713 |
On new SIB for neighbour cell information in IoT NTN |
Lenovo |
| R2-2306169 |
Mobility enhancement in IoT NTN |
Apple |
| R2-2306486 |
On IoT NTN CHO and other mobility enhancements |
Samsung Suzhou |
| 7.6.4 |
Enhancements to discontinuous coverage |
|
| R2-2304812 |
Discussion on discontinuous coverage |
Huawei, HiSilicon |
| R2-2304896 |
Discussion on enhancements to discontinuous coverage |
CATT |
| R2-2305171 |
IoT-NTN discontinuous coverage enhancements |
Interdigital, Inc. |
| R2-2305172 |
LS on PTW modification due to UE unreachability |
Interdigital, Inc. |
| R2-2305201 |
RRC release procedure in discontinuous coverage |
Qualcomm Incorporated |
| R2-2305307 |
Considerations on Supporting Discontinuous Coverage |
NEC Europe Ltd |
| R2-2305372 |
Discussion on enhancement to discontinuous coverage for IoT NTN |
Transsion Holdings |
| R2-2305560 |
Discussion on power saving enhancements for supporting discontinuous coverage |
Spreadtrum Communications |
| R2-2305612 |
Discussion on the discontinuous coverage for IoT-NTN |
CMCC |
| R2-2305672 |
Enhancements to discontinuous coverage |
Xiaomi |
| R2-2305714 |
Further considerations on discontinuous coverage |
Lenovo |
| R2-2305785 |
Enhancements to discontinuous coverage |
Samsung Shenzhen |
| R2-2305863 |
On RAN impacts for Discontineous coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2305959 |
RAN2 enhancements for discontinuous coverage |
ZTE Corporation, Sanechips |
| R2-2306167 |
Support on discontinuous coverage in IoT NTN |
Apple |
| R2-2306466 |
Enhancements to discontinuous coverage |
Ericsson |
| 7.7 |
NR NTN enhancements |
|
| R2-2305391 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| 7.7.1 |
Organizational |
|
| R2-2304634 |
LS on the system parameters for NTN above 10 GHz (R4-2305926; contact: CATT) |
RAN4 |
| R2-2305407 |
Stage 2 running CR for TS 38.300 for Rel-18 NTN |
THALES |
| R2-2305506 |
Discussion on NR NTN UE capabilities |
Intel Corporation |
| R2-2305507 |
Draft 306 CR for NR NTN UE capabilities |
Intel Corporation |
| R2-2305508 |
Draft 331 CR for NR NTN UE capabilities |
Intel Corporation |
| R2-2305933 |
Stage 3 NTN running CR for 38.321 - RAN2#121bise |
InterDigital |
| R2-2306294 |
Stage 3 running 38.304 CR for NTN |
ZTE corporation, Sanechips |
| R2-2306468 |
Stage 3 Running RRC CR for NR NTN Rel-18 |
Ericsson |
| R2-2306771 |
LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK (R1-2306105; contact: NTT DOCOMO) |
RAN1 |
| R2-2306955 |
Stage-3 running CR for TS 38.321 for Rel-18 NTN |
InterDigital |
| R2-2306960 |
Stage 2 running CR for TS 38.300 for Rel-18 NTN enhancements |
THALES (Rapporteur) |
| R2-2306961 |
Stage 3 running 38.304 CR for NTN |
ZTE corporation, Sanechips |
| R2-2306964 |
Stage 3 Running RRC CR for NR NTN Rel-18 |
Ericsson |
| 7.7.2 |
Coverage Enhancements |
|
| R2-2304743 |
Discussion on PUCCH enhancement for Msg4 HARQ-ACK in NR NTN |
OPPO |
| R2-2305744 |
Discussion on coverage enhancement |
Xiaomi |
| 7.7.3 |
Network verified UE location |
|
| R2-2304735 |
On Network Verified UE Location in NR NTN |
MediaTek Inc. |
| R2-2304811 |
Discussion on the network verfied UE location |
Huawei, Turkcell, HiSilicon |
| R2-2305033 |
Discussion on network verified UE location |
Ericsson |
| R2-2305194 |
Single satellite Multi-RTT based positioning |
Qualcomm Incorporated |
| R2-2305249 |
Discussion on multiple-RTT based positioning in NTN |
Quectel |
| R2-2305393 |
Discussion on NTN NW verified UE location |
Lenovo |
| R2-2305408 |
Discussion on network verified UE location in NR NTN |
THALES |
| R2-2305596 |
Network verified UE location |
CMCC |
| R2-2305673 |
Discussion on network verified UE location |
Xiaomi |
| R2-2305790 |
Remaining issues on Network Verified UE Location |
Samsung Shenzhen |
| R2-2305940 |
On Network verified UE location |
Nokia, Nokia Shanghai Bell |
| R2-2306244 |
Consideration on NW verified UE location and CE |
ZTE Corporation, Sanechips |
| R2-2306377 |
Discussion on Network Verified UE Location |
TCL Communication Ltd. |
| 7.7.4.1.1 |
NTN-TN enhancements |
|
| R2-2304696 |
Discussion on TN-NTN cell reselection enhancements |
CAICT |
| R2-2304744 |
Discussion on NTN-TN cell reselection enhancement |
OPPO |
| R2-2304783 |
Considerations on the NTN-TN cell re-selection enhancements |
Telit Communications S.p.A. |
| R2-2304834 |
Further discussion on power saving for NTN-TN mobility |
vivo |
| R2-2304897 |
Discussion on the mechanism for providing TN coverage information |
CATT |
| R2-2305048 |
Discussion on NTN-TN cell reselection enhancements |
Continental Automotive |
| R2-2305195 |
TN cell coverage info and measurement relaxation |
Qualcomm Incorporated |
| R2-2305373 |
Discussion on remaining issues of NTN-TN cell reselection enhancements |
Transsion Holdings |
| R2-2305597 |
Discussion on NTN-TN cell reselection enhancements |
CMCC |
| R2-2305674 |
Cell reselection enhancements for NTN-TN mobility |
Xiaomi |
| R2-2305715 |
Further discussions on indication of TN coverage information |
Lenovo |
| R2-2305866 |
Details of the TN coverage data signalling |
NEC Telecom MODUS Ltd. |
| R2-2305882 |
Resolving Open Issues on TN Coverage Definition |
Nokia, Nokia Shanghai Bell |
| R2-2305893 |
Discussion on the TN Coverage Information |
Google Inc. |
| R2-2305934 |
NTN-TN mobility and service continuity |
InterDigital |
| R2-2305994 |
NTN-TN Mobility Cell Reselection and PCI Values |
SHARP Corporation |
| R2-2306031 |
Discussion on providing TN coverage area information |
LG Electronics France |
| R2-2306070 |
Discussion on the NTN-TN cell reselection enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2306153 |
NTN-TN Cell Reselection Enhancement |
Apple |
| R2-2306324 |
Remaining issues on NTN-TN Cell Reselection Enhancements |
Samsung Research America |
| R2-2306352 |
Discussion on TN area information for the NTN-TN cell re-selection enhancements |
ETRI |
| R2-2306389 |
Discussion on NTN-TN Cell re-selection |
ITL |
| R2-2306467 |
TN NTN mobility enhancements |
Ericsson |
| R2-2306643 |
Report from [AT122][103][NR-NTN Enh] NTN-TN cell reselection (Nokia) |
Nokia, Nokia Shanghai Bell |
| 7.7.4.1.2 |
NTN-NTN enhancements |
|
| R2-2304698 |
Discussion on NTN-NTN cell reselection enhancements |
CAICT |
| R2-2304745 |
Discussion on NTN-NTN cell reselection enhancement |
OPPO |
| R2-2304835 |
Further discussion on cell reselection enhancments for earth-moving cell |
vivo |
| R2-2304898 |
Discussion on the cell reselection enhancement for earth-moving cell |
CATT, IPLOOK |
| R2-2305374 |
Discussion on remaining issues of NTN-NTN reselection enhancements |
Transsion Holdings |
| R2-2305561 |
Discussion on NTN-NTN mobility enhancements |
Spreadtrum Communications |
| R2-2305598 |
Discussion on NTN-NTN reselection |
CMCC |
| R2-2305666 |
Proposals for completing the decisions from last RAN2 meeting #121bis-e |
PANASONIC |
| R2-2305675 |
Cell reselection enhancements for NTN-NTN mobility |
Xiaomi |
| R2-2305716 |
Neighbour cell measurement triggering in NTN moving cells |
Lenovo |
| R2-2305935 |
Cell reselection enhancements for Earth moving cell |
InterDigital |
| R2-2306032 |
Discussion on NTN-NTN cell reselection enhancements |
LG Electronics France |
| R2-2306154 |
NTN-NTN Cell Reselection Enhancement |
Apple |
| R2-2306295 |
Consideration on cell reselection enhancements for NTN-NTN |
ZTE corporation, Sanechips,Intel Corporation |
| R2-2306325 |
Discussion on NTN-NTN Cell Reselection Enhancements |
Samsung Research America |
| R2-2306470 |
NTN NTN mobility enhancements |
Ericsson |
| R2-2306644 |
[AT122][104][NR-NTN Enh] Location-based cell reselection enhancements (CMCC) |
CMCC |
| 7.7.4.2 |
Handover enhancements |
|
| R2-2304734 |
Handover Enhancements in Earth Moving Cells |
MediaTek Inc. |
| R2-2304736 |
Enabling Group Handover in NR-NTN |
MediaTek Inc. |
| R2-2304753 |
Discussion on NTN handover enhancements |
OPPO |
| R2-2304833 |
Discussion on handover enhancement with common HO configuration in NR NTN |
vivo |
| R2-2304836 |
Further discusison on service link switching with unchanged PCI |
vivo |
| R2-2304899 |
Discussion on unchanged PCI scenario |
CATT |
| R2-2304900 |
Discussion on common (C)HO configuration and RACH-less |
CATT |
| R2-2305049 |
Discussion on NTN-NTN handover enhancements |
Continental Automotive |
| R2-2305152 |
Satellite switch_PCI change without L3 handover |
NEC |
| R2-2305153 |
Support RACH-less CHO |
NEC |
| R2-2305196 |
RACH-less handover for NTN |
Qualcomm Incorporated |
| R2-2305197 |
Satellite switch enhancements for NTN |
Qualcomm Incorporated |
| R2-2305238 |
Support of broadcasting HO signaling in NTN |
China Telecom |
| R2-2305375 |
Discussion on NTN-NTN handover enhancements |
Transsion Holdings |
| R2-2305380 |
Discussion on NTN handover enhancements |
TCL Communication Ltd. |
| R2-2305518 |
Signaling overhead reduction and group handover during NTN-NTN HOs |
Sony |
| R2-2305599 |
Discussion on handover enhancements for NTN |
CMCC |
| R2-2305676 |
Discussion on handover enhancements for NTN-NTN mobility |
Xiaomi |
| R2-2305717 |
Potential issues for RACH-less HO in NTN |
Lenovo |
| R2-2305883 |
Open Aspects on RACH-less HO in Rel-18 NTN |
Nokia, Nokia Shanghai Bell |
| R2-2305884 |
On Common and Conditional Handover Signalling in Rel-18 NTN |
Nokia, Nokia Shanghai Bell |
| R2-2305936 |
NTN mobility enhancements for RRC_CONNECTED |
InterDigital |
| R2-2305937 |
Satellite switching without PCI change |
InterDigital |
| R2-2306033 |
Discussion on handover enhancements |
LG Electronics France |
| R2-2306071 |
Remaining issues on RACH-less HO in NTN |
Huawei, HiSilicon, Turkcell |
| R2-2306072 |
Discussion on the Common (C)HO configuration |
Huawei, HiSilicon, Turkcell |
| R2-2306122 |
Discussion on handover enhancement with common signalling |
ASUSTeK |
| R2-2306123 |
Discussion on RACH-less handover for NTN |
ASUSTeK |
| R2-2306155 |
Signaling optimization on common HO configuration |
Apple |
| R2-2306156 |
NTN specific handover enhancement |
Apple |
| R2-2306296 |
Consideration on HO enhancements in NTN |
ZTE corporation, Sanechips |
| R2-2306326 |
Discussion on NTN Handover Enhancements |
Samsung Research America |
| R2-2306351 |
Discussion on the SMTC and Measurement Gap Enhancements |
Google Inc. |
| R2-2306370 |
Discussion on handover enhancements |
Sharp |
| R2-2306453 |
NTN-NTN handover enhancements |
Sequans Communications |
| R2-2306465 |
Handover enhancements |
Ericsson |
| R2-2306517 |
“Unchanged PCI” solution vs “PCI change only” solution |
Sequans Communications |
| R2-2306645 |
Summary of [AT122][105][NR-NTN Enh] Common signaling in (C)HO (OPPO) |
OPPO |
| R2-2306646 |
Summary of [AT122][106][NR-NTN Enh] RACH-less HO (Huawei) |
Huawei, HiSilicon |
| R2-2306666 |
DRAFT LS on common signaling in (C)HO |
OPPO |
| R2-2306922 |
LS on common signaling in ©HO |
RAN2 |
| 7.8.1 |
Organizational |
|
| R2-2305885 |
Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan |
Nokia, Nokia Shanghai Bell |
| R2-2305886 |
Stage-2 Text Proposal for Rel-18 UAVs |
Nokia, Nokia Shanghai Bell |
| R2-2306967 |
Introduction of UAV support in Rel-18 NR |
Nokia, Nokia Shanghai Bell |
| 7.8.2 |
Measurement reporting for mobility and interference control |
|
| R2-2305056 |
Measurement and reporting enhancements |
Qualcomm Incorporated |
| R2-2305143 |
On Height-dependent Measurement Report Configuration for UAVs |
Nokia, Nokia Shanghai Bell |
| R2-2305144 |
On Interference Reporting for UAVs |
Nokia, Nokia Shanghai Bell |
| R2-2305302 |
Discussion on Measurement Reports Enhancements |
NEC Europe Ltd |
| R2-2305429 |
Discussion on measurement reporting enhancement for NR UAV |
vivo |
| R2-2305600 |
Discussion on Measurement Reporting for NR UAV |
CMCC |
| R2-2305691 |
Discussion on height dependent measurement for NR UAV |
Lenovo |
| R2-2305868 |
UAV measurement reports |
Ericsson |
| R2-2306046 |
Remaining issues on measurement reporting enhancements in NR UAV |
Samsung Electronics Austria |
| R2-2306053 |
Discussion on measurement reporting for NR UAV |
Sharp |
| R2-2306135 |
Discussion on measurement reporting for NR UAV |
Xiaomi |
| R2-2306171 |
Measurement reporting enhancement in UAV |
Apple |
| R2-2306215 |
Measurement report enhancement for UAV |
Huawei, HiSilicon |
| R2-2306288 |
Measurement Report Enhancement |
LG Electronics |
| R2-2306337 |
Measurement reporting enhancements for NR UAV |
China Telecom Corporation Ltd. |
| R2-2306458 |
Further discussion on NR support for UAV |
NTT DOCOMO, INC. |
| R2-2306490 |
Measurement reporting enhancement in NR UAV |
ZTE Corporation, Sanechips |
| R2-2306491 |
Height-dependent measurement configuration |
ZTE Corporation, Sanechips |
| R2-2306529 |
Measurement reporting for mobility and interference control |
China Telecom |
| R2-2306800 |
Summary of [AT122][304][UAV] Height-dependent MR configuration (ZTE) |
ZTE Corporation, Sanechips |
| 7.8.3 |
Flight path reporting |
|
| R2-2305109 |
Delta reporting of flight path plan |
Qualcomm Incorporated |
| R2-2305304 |
Discussion on Flight Path Reporting |
NEC Europe Ltd |
| R2-2305430 |
discussion on Flight path reporting |
vivo |
| R2-2305544 |
UAV Flight Path Reporting |
Ericsson España S.A. |
| R2-2305601 |
Discussion on Flight path Reporting |
CMCC |
| R2-2305692 |
Remaining issues of flight path reporting for NR UAV |
Lenovo |
| R2-2305887 |
Further Details on Flight Path Plan (FPP) |
Nokia, Nokia Shanghai Bell |
| R2-2305938 |
Flightpath update notification for UAV |
InterDigital |
| R2-2305939 |
Flightpath reporting for UAV |
InterDigital |
| R2-2306054 |
Discussion on flight path reporting for NR UAV |
Sharp |
| R2-2306124 |
Discussion on triggering of flight path report |
ASUSTeK |
| R2-2306136 |
Discussion on flight path reporting for NR UAV |
Xiaomi |
| R2-2306170 |
Flight path reporting in UAV |
Apple |
| R2-2306216 |
Discussion on flight path reporting |
Huawei, HiSilicon |
| R2-2306236 |
Leftover Issue on Flight Path Reporting |
CATT |
| R2-2306241 |
Consideration on flight path reporting for NR UAV |
DENSO CORPORATION |
| R2-2306289 |
Flight Path Information Report |
LG Electronics |
| R2-2306338 |
Flight path reporting enhancements for NR UAV |
China Telecom Corporation Ltd. |
| R2-2306449 |
Discussion on flight path reporting |
Samsung |
| R2-2306492 |
On flight path reporting |
ZTE Corporation, Sanechips |
| 7.8.4 |
Subscription-based aerial-UE identification |
|
| R2-2305431 |
discussion on Subscription-based aerial-UE identification |
vivo |
| R2-2305545 |
Subscription-Based Aerial UEs Identification |
Ericsson España S.A |
| R2-2305602 |
Subscription-based aerial-UE identification for NR UAV |
CMCC |
| R2-2306030 |
Subscription-based Aerial-UE Identification in NR |
Qualcomm Incorporated |
| R2-2306048 |
Discussion on subscription-based aerial-UE identification for NR UAV |
Samsung Electronics Austria |
| R2-2306217 |
Consideration on subscription-based UAV identification |
Huawei, HiSilicon |
| R2-2306424 |
UAV Subscription and Identification |
Beijing Xiaomi Mobile Software |
| 7.8.5 |
UAV identification broadcast |
|
| R2-2305110 |
Remaining aspects of PC5-based BRID and DAA support |
Qualcomm Incorporated |
| R2-2305306 |
Considerations on Enhancements for UAV identification broadcast |
NEC Europe Ltd |
| R2-2305432 |
discussion on UAV identification broadcast |
vivo |
| R2-2305546 |
UAV Broadcast Identification |
Ericsson España S.A. |
| R2-2305603 |
UAV identification broadcast |
CMCC |
| R2-2305693 |
Discussion on broadcasting remote id for UAV |
Lenovo |
| R2-2305742 |
Resource configuration for UAV ID broadcast |
Samsung |
| R2-2305888 |
On How To Ensure QoS for PC5-based BRID and DAA |
Nokia, Nokia Shanghai Bell |
| R2-2306218 |
Discussion on UAV remote identification broadcast |
Huawei, HiSilicon |
| R2-2306425 |
NR UAV BRID broadcast over PC5 |
Beijing Xiaomi Mobile Software |
| R2-2306493 |
On UAV identification broadcast |
ZTE Corporation, Sanechips |
| 7.9.1 |
Organizational |
|
| R2-2304617 |
Reply LS on comparison of SL-RSRP and SD-RSRP measurements (R1-2304211; contact: Nokia) |
RAN1 |
| R2-2304637 |
LS on Comparison of SL-RSRP and SD-RSRP measurements (R4-2306366; contact: Nokia) |
RAN4 |
| R2-2304646 |
LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (S2-2207518; contact: LGE) |
SA2 |
| R2-2304652 |
Reply LS on 5G ProSe Layer-2 UE-to-UE Relay QoS enforcement (S2-2305915; contact: Qualcomm) |
SA2 |
| R2-2305207 |
Draft running CR 38.300 (initial) |
LG Electronics France |
| R2-2305208 |
Draft running CR 38.300 (update) |
LG Electronics France |
| R2-2306554 |
Draft running CR 38.300 |
LG Electronics |
| R2-2306843 |
Draft running CR 38.300 |
LG Electronics |
| 7.9.2 |
UE-to-UE relay |
|
| R2-2304680 |
SRAP design and Connection establishment |
NEC |
| R2-2304754 |
Discussion on U2U relay |
OPPO |
| R2-2304957 |
Discussion on the adaptation layer |
Fujitsu |
| R2-2305043 |
Further discussion on U2U Relay |
ZTE, Sanechips |
| R2-2305062 |
Discussion on UE-to-UE Relay |
Apple |
| R2-2305180 |
Discovery and Relay Selection for UE-to-UE Relays |
InterDigital |
| R2-2305181 |
QoS and Adaptation Layer for UE-to-UE Relays |
InterDigital |
| R2-2305210 |
Control plane procedure and adaptaion layer for U2U relay |
LG Electronics France |
| R2-2305233 |
Discussion on U2U sidelink relay |
China Telecom |
| R2-2305245 |
Discussion on the common L2 L3 parts for U2U relaying |
vivo |
| R2-2305246 |
Discussion on the L2 specific parts for U2U relaying |
vivo |
| R2-2305279 |
Discussion on U2U Relay |
CATT |
| R2-2305519 |
UE-to-UE relay (re)selection |
Sony |
| R2-2305520 |
Discussion on DRX for Sidelink UE to UE Relay |
Sony |
| R2-2305547 |
Discussion on Relay (re)selection and Discovery |
Ericsson España S.A. |
| R2-2305548 |
Control Plane Procedures for Layer 2 UE-to-UE Relays |
Ericsson España S.A. |
| R2-2305551 |
Discussion on UE-to-UE relay |
Spreadtrum Communications |
| R2-2305590 |
Considerations on U2U relay (re)selection and Local ID assignment |
Nokia, Nokia Shanghai Bell |
| R2-2305618 |
Discussion on U2U relay |
CMCC |
| R2-2305697 |
Discussion on L2 U2U relay |
Lenovo |
| R2-2305743 |
QoS split and Bearer configuration |
Samsung |
| R2-2305762 |
Layer-2 specific part on U2U Relay |
Qualcomm Incorporated |
| R2-2305763 |
gNB involvement on U2U relay |
Qualcomm Incorporated |
| R2-2305802 |
SRAP design for U2U Sidelink Relay |
Samsung R&D Institute UK |
| R2-2305874 |
Considerations for U2U L2 relay operations |
Kyocera |
| R2-2306125 |
Discussion on aspects of AS layer configuration for L2 U2U Relay |
ASUSTeK |
| R2-2306126 |
Discussion on E2E PC5-RRC configurations |
ASUSTeK |
| R2-2306191 |
Discussion on UE-to-UE relay |
Huawei, HiSilicon |
| R2-2306378 |
Discussion on L2 U2U Relay |
MediaTek Inc. |
| R2-2306380 |
Remaining issues for U2U relay |
Sharp |
| R2-2306427 |
U2U Relay UE discovery / (re)selection, SRAP, QoS Handling |
Beijing Xiaomi Mobile Software |
| R2-2306555 |
Summary of AI 7.9.2 on UE-to-UE relay |
ZTE, Sanechips |
| R2-2306690 |
Summary of [AT122][418][Relay] Authorisation for U2U relay (ZTE) |
ZTE (Rapporteur) |
| R2-2306691 |
Reply LS on ProSe Authorization information related to UE-to-UE Relay operation |
RAN2 |
| R2-2306692 |
[AT122][419][Relay] Short ID in U2U relay (Ericsson) |
Ericsson |
| R2-2306697 |
LS on announcement of neighbor UEs |
RAN2 |
| R2-2306889 |
Reply LS on ProSe Authorization information related to UE-to-UE Relay operation |
RAN2 |
| 7.9.3 |
Service continuity enhancements for L2 UE-to-network relay |
|
| R2-2304681 |
DRAFT LS for Draft LS to RAN3 on Lossless Path Switching for Sidelink Relay |
NEC |
| R2-2304755 |
Discussion on lossless data forwarding for inter-gNB service continuity |
OPPO |
| R2-2305025 |
Discussion on lossless path switching for Sidelink Relay |
CANON Research Centre France |
| R2-2305044 |
Further discussion on service continuity for SL relay |
ZTE, Sanechips |
| R2-2305063 |
Discussion on Service continuity enhancement of L2 U2N relay |
Apple |
| R2-2305182 |
Remaining Issues on Service Continuity |
InterDigital |
| R2-2305209 |
SL U2N relay for the service continuity enhancement |
LG Electronics France |
| R2-2305217 |
Discussion on service continuity enhancement |
Xiaomi |
| R2-2305234 |
Discussion on lossless delivery solution for inter-gNB path switching |
China Telecom |
| R2-2305247 |
Remaining issues on service continuity enhancement for L2 U2N relay |
vivo |
| R2-2305280 |
Further Consideration on Service Continuity Enhancements for L2 U2N Relay |
CATT |
| R2-2305419 |
Discussion on reply LSs on RSRP issues (R1-2304211 / R2-2304617 and R4-2306366 / R2-2304637) |
Nokia, Nokia Shanghai Bell |
| R2-2305420 |
Discussion on L2 U2N relay service continuity issues for inter-gNB path switch |
Nokia, Nokia Shanghai Bell |
| R2-2305521 |
Service continuity enhancements for UE sidelink relay |
Sony |
| R2-2305549 |
Discussion on Inter-gNB Service Continuity |
Ericsson España S.A. |
| R2-2305552 |
Service continuity enhancements support for L2 U2N relay |
Spreadtrum Communications |
| R2-2305585 |
Service Continuity Enhancements and Lossless Data Delivery |
NEC Corporation |
| R2-2305619 |
Discussion on service continuity |
CMCC |
| R2-2305761 |
Lossless Inter-gNB path switching |
Lenovo |
| R2-2305764 |
Evaluation and proposals on U3 and U5 |
Qualcomm Incorporated, OPPO, Xiaomi |
| R2-2305979 |
Discussion on Service Continuity |
Huawei, HiSilicon |
| R2-2306260 |
Remaining issues for service continuity |
MediaTek Inc. |
| R2-2306374 |
Discussion on Event Z2 |
Samsung |
| R2-2306381 |
remaining issues for i2x path switching with lossless delivery |
Sharp |
| R2-2306383 |
Discussion on remaining issues for path switching |
Sharp |
| R2-2306559 |
Summary of AI 7.9.3 on service continuity (vivo) |
vivo |
| 7.9.4 |
Multi-path relaying |
|
| R2-2304664 |
Discussion on multi-path SL relay |
OPPO |
| R2-2304958 |
Discussions on multi-path |
Fujitsu |
| R2-2305008 |
Discussion sidelink relay enhancement for scenario 1&2 |
Samsung |
| R2-2305045 |
Discussion on the RAN2 impacts of multi-path relaying with CU/DU split architecture |
ZTE, OPPO |
| R2-2305046 |
Further discussion on the support of multi-path relaying |
ZTE, Sanechips |
| R2-2305064 |
Discussion on Multi-path Relay |
Apple |
| R2-2305183 |
Design Aspects for Multi-path |
InterDigital |
| R2-2305218 |
Discussion on multi-path |
Xiaomi |
| R2-2305232 |
Discussion on the mode 1 RA issue under multi-path scenario |
NEC, Nokia,OPPO,ZTE,Huawei, HiSilicon, Sharp, Samsung, Philips, MediaTek |
| R2-2305235 |
Discussion on remaining issues of multi-path relaying |
China Telecom |
| R2-2305248 |
Remaining Issues for Multi-path Scenario-1 and Scenario-2 |
vivo |
| R2-2305281 |
Discussion on Multi-path Scenario 1 |
CATT |
| R2-2305282 |
Leftover issues on Multi-path scenario2 |
CATT |
| R2-2305522 |
Multi-path relaying discussion |
Sony |
| R2-2305550 |
Discussion on Multipath Relays |
Ericsson España S.A. |
| R2-2305553 |
Discussion on multi-path relaying |
Spreadtrum Communications |
| R2-2305586 |
Discussion on Multi-path Relaying |
NEC Corporation |
| R2-2305620 |
Discussion on multi-path scenario 1 |
CMCC |
| R2-2305621 |
Considerations on multi-path scenario 2 |
CMCC |
| R2-2305698 |
Procedure for second path addition |
Lenovo |
| R2-2305765 |
Address controversial issues on multi-path relay |
Qualcomm Incorporated |
| R2-2305873 |
Considerations for multipath relay operations for Scenario 1 |
Kyocera |
| R2-2305945 |
Discussion on Multi-path relaying |
Lenovo |
| R2-2306127 |
Resource allocation and BSR reporting for multi-path |
ASUSTeK |
| R2-2306192 |
Remaining issues on multi-path operation |
Huawei, HiSilicon |
| R2-2306310 |
Discussion on multi-path scenario 1 |
III |
| R2-2306313 |
Multipath SL relay |
Nokia, Na Shanghai Bell |
| R2-2306355 |
Multi-path relaying for NR sidelink relay enhancements |
LG Electronics France |
| R2-2306382 |
Remaining issues for multi-path relay |
Sharp |
| R2-2306445 |
Discussion on Multipath |
MediaTek Inc. |
| R2-2306497 |
About Throughput Enhancements in Sidelink Multi-Path Relaying |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2306556 |
Discussion on multi-path SL relay |
OPPO |
| R2-2306672 |
[AT122][402][Relay] Multi-path relay summary proposals (OPPO) |
OPPO |
| R2-2306693 |
LS on Reporting of Relay UE C-RNTI and NCGI |
RAN2 |
| R2-2306694 |
LS to RAN3 on mode 1 scheduling in inter-DU multi-path case |
NEC |
| R2-2306781 |
LS to RAN3 on mode 1 scheduling in inter-DU multi-path case |
RAN2 |
| 7.9.5 |
DRX |
|
| R2-2304756 |
Discussion on DRX for L2 U2N relay |
OPPO |
| R2-2305065 |
Discussion on SL DRX for L2 UE-to-NW relay |
Apple |
| R2-2305219 |
Discussion on SL DRX in U2N relay |
Xiaomi |
| R2-2305592 |
Considerations on paging for sidelink relay |
Nokia, Nokia Shanghai Bell |
| R2-2306193 |
Left issues on sidelink DRX for L2 U2N relay |
Huawei, HiSilicon |
| 7.10.1 |
Organizational |
|
| R2-2305446 |
Introduction of Rel-18 IDC UE capabilities |
Intel Corporation |
| R2-2305447 |
Introcution of Rel-18 IDC UE capabilities |
Intel Corporation |
| R2-2305578 |
38.331 running CR for introduction of IDC |
Xiaomi |
| R2-2305579 |
Draft LS on autonomous denial |
Xiaomi |
| R2-2305580 |
Summary of [Post121][655][IDC] Discussion on Leftover issues for IDC |
Xiaomi |
| R2-2305995 |
Introduction of In-Device Co-existence (IDC) enhancements for NR |
Huawei, HiSilicon |
| R2-2306304 |
37.340 Running CR for Introduction of IDC |
ZTE Corporation, Sanechips |
| R2-2306591 |
38.331 running CR for introduction of IDC |
Xiaomi |
| R2-2306592 |
Introduction of In-Device Co-existence (IDC) enhancements for NR |
Huawei, HiSilicon |
| R2-2306593 |
37.340 Running CR for Introduction of IDC |
ZTE Corporation, Sanechips |
| R2-2306594 |
LS on autonomous denial |
RAN2 |
| R2-2306595 |
[AT122][655][IDC] Discussion on inter-node coordination solution (Huawei) |
Huawei, HiSilicon, Ericsson |
| R2-2306907 |
37.340 Running CR for Introduction of IDC |
ZTE Corporation, Sanechips |
| R2-2306923 |
Introduction of In-Device Co-existence (IDC) enhancements for NR |
Huawei, HiSilicon |
| R2-2306925 |
38.331 running CR for introduction of IDC |
Xiaomi |
| 7.10.2 |
FDM solution enhancements |
|
| R2-2305009 |
Discussion on inter-node coordination for IDC |
Samsung |
| R2-2305034 |
More granular FDM indications |
Ericsson |
| R2-2305035 |
IDC configuration and report in MR-DC |
Ericsson |
| R2-2305124 |
FDM Solutions in IDC |
Qualcomm Incorporated |
| R2-2305452 |
Open issues of FDM solution for IDC |
Intel Corporation |
| R2-2305581 |
Remaining issues for FDM |
Xiaomi |
| R2-2305976 |
Discussion on inter-node coordination issue for NR IDC |
Huawei, HiSilicon |
| R2-2305977 |
Leftover issues for FDM solution enhancement for NR IDC |
Huawei, HiSilicon |
| R2-2305978 |
Discussion on the handling IDC issue during the SDT procedure |
Huawei, HiSilicon |
| R2-2306210 |
Discussion on the leftover issue for IDC FDM Solution |
vivo |
| R2-2306305 |
Remaining Issues on the FDM solution enhancement |
ZTE Corporation, Sanechips |
| R2-2306307 |
Further Consideration on the NR-DC IMD Interference Reporting |
ZTE Corporation, Sanechips |
| R2-2306364 |
Common FDM and TDM aspects |
Nokia, Nokia Shanghai Bell |
| R2-2306366 |
Autonomous Denial Aspects |
Nokia, Nokia Shanghai Bell |
| 7.10.3 |
TDM solution |
|
| R2-2305125 |
TDM Solutions in IDC |
Qualcomm Incorporated |
| R2-2305453 |
Open issues of TDM solution for IDC |
Intel Corporation |
| R2-2305582 |
Remaining issues for TDM solutions |
Xiaomi |
| R2-2306173 |
Leftover autonomous denial operation issues in IDC |
Apple |
| R2-2306211 |
Discussion on the leftover issue for IDC TDM Solution |
vivo |
| R2-2306306 |
Remaining Issues on the TDM solution enhancement |
ZTE Corporation, Sanechips |
| R2-2306365 |
Interference direction for TDM Assistance Information for IDC |
Nokia, Nokia Shanghai Bell |
| 7.10.4 |
UE capabilities |
|
| R2-2305126 |
IDC UE Capabilities |
Qualcomm Incorporated |
| R2-2306212 |
Discussion on IDC UE Capabilities |
vivo |
| 7.11.1 |
Organizational |
|
| R2-2304819 |
RRC running CR for eMBS |
Huawei, HiSilicon |
| R2-2305631 |
38.300 Running CR for MBS enhancements |
CMCC |
| R2-2306157 |
MAC running CR for eMBS |
Apple |
| R2-2306854 |
38.300 Running CR for MBS enhancements |
CMCC |
| R2-2306855 |
RRC running CR for eMBS |
Huawei, HiSilicon |
| R2-2306856 |
MAC running CR for eMBS |
Apple |
| 7.11.2.1 |
Control plane |
|
| R2-2304700 |
Discussion on eMBS from the CP Perspective |
vivo Mobile Com. (Chongqing) |
| R2-2304728 |
Control plane discussion for multicast reception in RRC INACTIVE |
MediaTek inc. |
| R2-2304774 |
CP Issues of Multicast Reception in RRC_INACTIVE |
CATT, CBN |
| R2-2304820 |
Multicast reception for RRC_INACTIVE UE |
Huawei, HiSilicon |
| R2-2304933 |
Consideration on the control plane issue for multicast reception in RRC_INACTIVE |
Beijing Xiaomi Software Tech |
| R2-2304985 |
Discussion on control plane for Multicast reception in RRC_INACTIVE |
NEC Corporation |
| R2-2305184 |
Service continuity, RRC state transitions and notifications |
Qualcomm Incorporated |
| R2-2305379 |
Discussion for UEs receiving Multicast in RRC_INACTIVE state |
TCL Communication Ltd. |
| R2-2305387 |
Discussion on security issue with multicast MCCH |
CANON Research Centre France |
| R2-2305475 |
Control plane for multicast reception in RRC_INACTIVE state |
TD Tech, Chengdu TD Tech |
| R2-2305477 |
PTM configuration for multicast reception in RRC_INACTIVE |
LG Electronics Inc. |
| R2-2305478 |
Multicast activationdeactivation notification and RRC state transitions |
LG Electronics Inc. |
| R2-2305572 |
Discussion on Service Continuity and RRC state transitions |
Spreadtrum Communications |
| R2-2305632 |
Discussion on multicast reception in RRC_INACTIVE CP issues |
CMCC |
| R2-2305699 |
Discussion on PTM Configuration and Session Status Change |
Lenovo |
| R2-2305700 |
Discussion on Mobility and RRC State Transition |
Lenovo |
| R2-2305786 |
CP aspects for Multicast reception in RRC_INACTIVE |
Samsung R&D Institute India |
| R2-2305817 |
Transition to CONNECTED to ensure the reliability for an MBS session |
Interdigital Inc. |
| R2-2305916 |
Multicast reception in RRC_INACTIVE |
Ericsson |
| R2-2305917 |
MBS multicast and UE power saving |
Ericsson |
| R2-2306047 |
Notification of Multicast session deactivation/temporary no data in enhanced group paging message |
SHARP Corporation |
| R2-2306049 |
RRC Resume for Multicast in RRC_INACTIVE |
SHARP Corporation |
| R2-2306147 |
Control plane aspects on multicast reception in RRC INACTIVE |
Kyocera |
| R2-2306158 |
CP issues on multicast reception in RRC_INACTIVE |
Apple |
| R2-2306321 |
Control plane aspects for multicast reception in RRC_INACTIVE |
Intel Corporation |
| R2-2306363 |
PTM configuration and mobility handling |
Nokia, Nokia Shanghai Bell |
| R2-2306401 |
PTM configuration for multicast reception in RRC_INACTIVE |
Shanghai Jiao Tong University |
| R2-2306870 |
Report of [AT122][603][MBS] Session deactivation for MC in INACTIVE (Apple) |
Apple |
| 7.11.2.2 |
User plane |
|
| R2-2305663 |
CFR design for Multicast reception in RRC_INACTIVE |
ZTE, Sanechips |
| 7.11.3 |
Shared processing for MBS broadcast and Unicast reception |
|
| R2-2304701 |
Further Discussion on Shared Processing in eMBS |
vivo Mobile Com. (Chongqing) |
| R2-2304729 |
Discuss on Shared processing for broadcast and unicast reception |
MediaTek inc. |
| R2-2304775 |
Remaining issues on Shared Processing |
CATT, CBN |
| R2-2304821 |
Discussion on shared processing for MBS broadcast and unicast reception |
Huawei, HiSilicon |
| R2-2304888 |
Bandwidth signalling and scenarios for shared processing |
Nokia, Nokia Shanghai Bell |
| R2-2304986 |
Discussion on shared process for MBS broadcast and unicast |
NEC Corporation |
| R2-2305185 |
Shared processing for MBS broadcast and Unicast reception |
Qualcomm Incorporated |
| R2-2305480 |
Simultaneous unicast reception and broadcast reception |
TD Tech, Chengdu TD Tech |
| R2-2305502 |
Shared processing for simultaneous MBS broadcast and unicast reception |
Intel Corporation |
| R2-2305577 |
Remaining issues for shared processing of MBS |
Xiaomi |
| R2-2305633 |
Discussion on Shared processing |
CMCC |
| R2-2305664 |
Shared processing for MBS broadcast and unicast reception |
ZTE, Sanechips |
| R2-2305783 |
Shared processing for MBS broadcast and unicast reception |
Samsung R&D Institute India |
| R2-2306148 |
Shared processing for inter-PLMN MBS broadcast reception |
Kyocera |
| R2-2306159 |
Shared processing of MBS broadcast and unicast reception |
Apple |
| 7.12 |
Mobile IAB (Integrated Access and Backhaul) for NR |
|
| R2-2305026 |
Discussion on mobility enhancements for mobile IAB |
CANON Research Centre France |
| 7.12.1 |
Organizational |
|
| R2-2305154 |
Workplan for Rel-18 mobile IAB |
Qualcomm Inc. (Rapporteur) |
| 7.12.2.1 |
Connected mode |
|
| R2-2304695 |
Discussion on RACH-less HO in R18 NR |
Xiaomi |
| R2-2304768 |
Discussion on CHO enhancement for mIAB |
Xiaomi |
| R2-2304992 |
RACH-less and CHO for mobile IAB |
Huawei, HiSilicon |
| R2-2305040 |
Discussion on mobility enhancement for UE in connected mode |
ZTE, Sanechips |
| R2-2305053 |
Support for RACH-less HO and CHO in mobile IAB |
Nokia, Nokia Shanghai Bell |
| R2-2305095 |
UE on-board status identification and reporting |
Apple, Huawei, HiSilicon, Lenovo, CATT, InterDigital Inc. |
| R2-2305096 |
CONNECTED mobility enhancement in mobile IAB |
Apple |
| R2-2305155 |
Enhancements for mobile IAB connected mode mobility |
Qualcomm Inc. |
| R2-2305240 |
Connected mode mobility enhancements for mobile IAB |
CATT |
| R2-2305460 |
Discussion on mobility enhancements for mobile IAB |
NEC Corporation |
| R2-2305498 |
Mobile IAB mobility enhancement for connected UEs |
Intel Corporation |
| R2-2305591 |
Time-based CHO for mobile IAB |
SHARP Corporation |
| R2-2305701 |
Mobility enhancements for mobile IAB-node and its connected UE |
Lenovo |
| R2-2305818 |
Connected mode mobility enhancements for mobile IAB |
Interdigital Inc. |
| R2-2305993 |
CHO for mobile IAB scenario |
InterDigital Inc. |
| R2-2306009 |
Issues on supporting RACH-less for mobile IAB |
Ericsson |
| R2-2306149 |
Details of connected mode mobility enhancements for mobile IAB |
Kyocera |
| R2-2306184 |
Discussion on CHO enhancement for mIAB |
Xiaomi |
| R2-2306267 |
Enhancements for IAB-node mobility and onboard UEs |
AT&T |
| R2-2306277 |
Connected mode mobility enhancements |
LG Electronics France |
| R2-2306357 |
Discussion on RACH-less HO for mIAB |
KDDI Corporation |
| R2-2306488 |
Discussion on mIAB connected mode mobility enhancements |
Samsung Suzhou |
| R2-2306755 |
Discussion on mIAB connected mode mobility enhancements |
Samsung |
| R2-2306817 |
LS on UE RACH-less handover for mobile IAB |
RAN2 |
| 7.12.2.2 |
Idle/Inactive mode |
|
| R2-2304797 |
Discussion on cell reselection in mIAB |
Xiaomi |
| R2-2304993 |
Idle/Inactive mode UE mobility enhancement for mobile IAB |
Huawei, HiSilicon |
| R2-2305041 |
Discussion on mobility enhancement for UE in idle or inactive mode |
ZTE, Sanechips |
| R2-2305054 |
Autonomous search for mobile IAB cells |
Nokia, Nokia Shanghai Bell |
| R2-2305097 |
Discussion on IDLE/INACTIVE UE mobility enhancement |
Apple |
| R2-2305156 |
Enhancements for mobile IAB idle and inactive mode mobility |
Qualcomm Inc. |
| R2-2305241 |
Idle mode mobility enhancement for mobile IAB |
CATT |
| R2-2305499 |
UE cell (re)selection towards mobile IAB cell |
Intel Corporation |
| R2-2305523 |
Mobile IAB cell indication to UE behaviour |
Sony |
| R2-2305659 |
UE prioritization in cell reselection for mobile-IAB cells |
SHARP Corporation |
| R2-2305819 |
IDLE/INACTIVE mobility enhancements for mobile IAB |
Interdigital Inc. |
| R2-2306007 |
Behaviour for IDLE mode UEs under a mIAB node |
Ericsson |
| R2-2306008 |
Consideration of CAG feature for mobile IAB |
Ericsson |
| R2-2306138 |
Discussion on the cell reselection and cell type indication aspects |
Samsung R&D Institute UK |
| R2-2306150 |
IDLE/INACTIVE mode mobility enhancements for mobile IAB |
Kyocera |
| R2-2306183 |
Mobile IAB remaining issues |
vivo |
| R2-2306278 |
Access restriction during migration and cell reselection enhancement |
LG Electronics France |
| R2-2306871 |
Summary of [AT122][033][mIAB] Usage of the mIAB cell indication (Intel) |
Intel Corporation |
| R2-2306874 |
LS on CAG solution for mobile IAB |
Ericsson |
| R2-2306895 |
LS on CAG solution for mobile IAB |
RAN2 |
| 7.12.3 |
Other |
|
| R2-2304994 |
BAP impacts and RANAC issues |
Huawei, HiSilicon |
| R2-2305042 |
Discussion on Miscellaneous issues for mobile IAB node |
ZTE, Sanechips |
| R2-2305055 |
Mobile IAB BAP configuration issues |
Nokia, Nokia Shanghai Bell |
| R2-2305500 |
TAC/RANAC update of mobile IAB-node |
Intel Corporation |
| R2-2305524 |
PCI collision in mobile IAB |
Sony |
| R2-2305702 |
Discussion on BAP related issues for mobile IAB |
Lenovo |
| R2-2305801 |
Interference mitigation and PCI collision |
Samsung R&D Institute UK |
| R2-2306317 |
Remaining BAP issues on full migration |
LG Electronics Inc. |
| R2-2306818 |
Summary of [AT122][030][mIAB] BAP impacts |
Huawei, HiSilicon |
| 7.13.1 |
Organizational |
|
| R2-2304622 |
LS on MRO for CPC and CPA and fast MCG recovery (R3-230992; contact: Huawei) |
RAN3 |
| R2-2304628 |
LS on potential override of logged MDT reports upon moving from SNPN to PLMN (R3-232118; contact: Ericsson) |
RAN3 |
| R2-2304630 |
LS on intra-system inter-RAT SHR and SPR (R3-232140; contact: Huawei) |
RAN3 |
| R2-2304631 |
Reply LS on RACH enhancement for R18 SONMDT (R3-232144; contact: Huawei) |
RAN3 |
| R2-2304656 |
Reply LS on user consent of Non-public Network (S3-231399; contact: Vodafone) |
SA3 |
| R2-2305986 |
Running CR for Rel-18 SON MRO |
Ericsson |
| R2-2306100 |
Discussion on RAN2 impacts due to the LS R3-232144 |
Huawei, HiSilicon |
| R2-2306290 |
Discussion on RAN2 impacts due to the LS R3-232140 |
Huawei, HiSilicon |
| R2-2306452 |
Summary of AI 7.13.5 SON for NR-U (Ericsson) |
Ericsson |
| R2-2306530 |
Running 36.331 CR for SN RACH report |
ZTE Corporation, Sanechips |
| R2-2306531 |
Running 38.331 CR for RACH report |
ZTE Corporation, Sanechips |
| R2-2306753 |
Running 38.331 CR for logged MDT enhancements and NPN |
Huawei, HiSilicon |
| R2-2306754 |
Running 36.331 CR for logged MDT enhancements |
Huawei, HiSilicon |
| 7.13.2 |
MRO for inter-system handover for voice fallback |
|
| R2-2305483 |
Further Consideration on Inter-system Handover for Voice Fallback |
CATT |
| R2-2305678 |
MRO for inter-system handover for voice fallback |
Samsung R&D Institute India |
| R2-2305703 |
MRO for inter-system handover for voice fallback |
Lenovo |
| R2-2305722 |
MRO for inter-system handover for voice fallback |
Samsung R&D Institute India |
| R2-2305778 |
Further consideration on voice fallback |
CMCC |
| R2-2305987 |
Mobility Robustness Optimization – all topics |
Ericsson |
| R2-2306042 |
Data collection for MRO for inter-system handover for voice fallback |
Qualcomm Incorporated |
| R2-2306245 |
Consideration on MRO for inter-system handover for voice fallback |
ZTE Corporation, Sanechips |
| R2-2306291 |
Discussion on MRO for inter-system handover for voice fallback |
Huawei, HiSilicon |
| R2-2306455 |
Discussion on inter-system HO for voice fallback |
NTT DOCOMO, INC. |
| R2-2306761 |
Summary for 7.13.2 MRO for inter-system handover for voice fallback (Nokia) |
Nokia (Rapporteur) |
| 7.13.3 |
MDT override |
|
| R2-2304932 |
Considerations on MDT override enhancement for E-UTRAN |
Beijing Xiaomi Software Tech |
| R2-2305273 |
Discussion on MDT override protection |
LG Electronics |
| R2-2305421 |
Signalling based logged MDT override protection |
Nokia, Nokia Shanghai Bell |
| R2-2305988 |
MDT enhancements |
Ericsson |
| 7.13.4 |
SHR and SPCR |
|
| R2-2305324 |
Remaining issues on SPR |
vivo |
| R2-2305422 |
Discussion on SON for inter-RAT SHR |
Nokia, Nokia Shanghai Bell |
| R2-2305423 |
SPR and SHR related enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2305484 |
Further discussion on inter-RAT SHR and SPR |
CATT |
| R2-2305617 |
SON enhancement for SPR |
CMCC |
| R2-2305667 |
SON/MDT enhancements for SHR and SPR |
Samsung R&D Institute India |
| R2-2305704 |
Discussion on Successful Handover Report |
Lenovo |
| R2-2305705 |
SON enhancements for SPR |
Lenovo |
| R2-2306204 |
SON enhancement for SPR |
SHARP Corporation |
| R2-2306246 |
Remaining issues on SHR and SPCR |
ZTE Corporation, Sanechips |
| R2-2306292 |
Discussion on SHR and SPR |
Huawei, HiSilicon |
| R2-2306462 |
Discussion on SPR |
NTT DOCOMO, INC. |
| R2-2306752 |
Pre-meeting summary of 7.13.4 |
Huawei |
| R2-2306846 |
[DRAFT] Reply LS on intra-system inter-RAT SHR and SPR |
Huawei |
| R2-2306896 |
Reply LS on SHR and SPR |
RAN2 |
| 7.13.5 |
SON for NR-U |
|
| R2-2305424 |
Discussion on SON for NR-U |
Nokia, Nokia Shanghai Bell |
| R2-2305485 |
SON Enhancement for NR-U |
CATT |
| R2-2305658 |
SON/MDT enhancements for NR-U |
Samsung R&D Institute India |
| R2-2305706 |
Discussion on MRO for NR-U |
Lenovo |
| R2-2305728 |
Discussion on SON for NR-U |
Xiaomi |
| R2-2305777 |
SONMDT enhancement for NR-U |
CMCC |
| R2-2306043 |
Discussion on NR-U Related Enhancements |
Qualcomm Incorporated |
| R2-2306101 |
Discussion on SON for NR-U |
Huawei, HiSilicon |
| R2-2306247 |
Consideration on NR-U related SON |
ZTE Corporation, Sanechips |
| R2-2306450 |
Enhancements of SON reports for NR-U |
Ericsson |
| R2-2306557 |
Summary of AI 7.13.5 SON for NR-U (Ericsson) |
Ericsson |
| R2-2306558 |
Open issues and proposals on AI 7.13.5 SON for NR-U (Ericsson) |
Ericsson |
| 7.13.6 |
RACH enhancement |
|
| R2-2304930 |
Consideration on the SON enhancements for RACH report |
Beijing Xiaomi Software Tech |
| R2-2305070 |
SON enhancements for RACH |
Apple |
| R2-2305425 |
Discussion on RACH enhancement for SON |
Nokia, Nokia Shanghai Bell |
| R2-2305486 |
RACH enhancement for SON |
CATT |
| R2-2305616 |
Further considerations on RACH Enhancement |
CMCC |
| R2-2305660 |
SON/MDT enhancements for RACH |
Samsung R&D Institute India |
| R2-2305661 |
SON/MDT enhancements for RACH |
Samsung R&D Institute India |
| R2-2305989 |
RA report enhancement |
Ericsson |
| R2-2306102 |
Discussion on RACH enhancement |
Huawei, HiSilicon |
| R2-2306207 |
SON enhancement for RA report |
SHARP Corporation |
| R2-2306248 |
Consideration on RACH enhancements |
ZTE Corporation, Sanechips |
| R2-2306339 |
Further Discussion on RACH enhancements for SON |
China Telecom Corporation Ltd. |
| R2-2306760 |
Summary of 7.13.6 RACH enhancement (ZTE) |
ZTE Corporation, Sanechips |
| R2-2306848 |
Reply LS on RACH enhancement |
RAN2 |
| 7.13.7 |
SON/MDT enhancements for Non-Public Networks |
|
| R2-2304931 |
Discussion on the SONMDT enhancement for NPN |
Beijing Xiaomi Software Tech |
| R2-2305325 |
Discussion on SON enhancements for NPN |
vivo |
| R2-2305426 |
Discussion on NP related issues in SON/MDT |
Nokia, Nokia Shanghai Bell |
| R2-2305487 |
SON and MDT Enhancement for NPN |
CATT |
| R2-2305647 |
SON/MDT enhancements for NPN |
Samsung R&D Institute India |
| R2-2305990 |
SON support for NPN |
Ericsson |
| R2-2306249 |
Consideration on SON-MDT support for NPN |
ZTE Corporation, Sanechips |
| R2-2306293 |
Discussion on SONMDT enhancements for NPN |
Huawei, HiSilicon |
| R2-2306358 |
Discussion on the “LS on potential override of logged MDT reports upon moving from SNPN to PLMN” from RAN3 (R3-232118) |
Beijing Xiaomi Software Tech |
| R2-2306764 |
Summary of 7.13.7 SONMDT enhancements for NPN (CATT) |
CATT |
| 7.13.8 |
Other |
|
| R2-2305326 |
Discussion on MRO for CPAC |
vivo |
| R2-2305340 |
SON on fast MCG recovery |
OPPO |
| R2-2305488 |
Discussion on Fast MCG recovery and MHI Enhancement |
CATT |
| R2-2305707 |
SON enhancements for CPAC |
Lenovo |
| R2-2305708 |
MRO for fast MCG link recovery |
Lenovo |
| R2-2305779 |
Further considerations on fast MCG recovery |
CMCC |
| R2-2305780 |
SON MDT enhancement for MR-DC CPAC |
CMCC |
| R2-2305781 |
MHI Enhancement for SCG Activation Deactivation |
CMCC, Ericsson, CATT |
| R2-2305991 |
RAN observability issues for DRBs with stringent QoS requirements |
Ericsson |
| R2-2306103 |
Discussion on Fast MCG recovery, CPAC and MDT overide |
Huawei, HiSilicon |
| R2-2306209 |
Discussion on failure information for CPAC |
SHARP Corporation |
| R2-2306219 |
MRO for fast MCG recovery |
SHARP Corporation |
| R2-2306250 |
Remaining issues on fast MCG recovery enhancement |
ZTE Corporation, Sanechips |
| R2-2306390 |
MRO for Fast MCG Recovery, CPAC and SCGFailureInformation |
Samsung R&D Institute India |
| R2-2306391 |
MRO for Fast MCG Recovery, CPAC and SCGFailureInformation |
Samsung R&D Institute India |
| R2-2306456 |
Discussion on CPAC failure report |
NTT DOCOMO, INC. |
| 7.14.1 |
Organizational |
|
| R2-2304625 |
LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload (R3-232047; contact: ZTE) |
RAN3 |
| R2-2304626 |
LS on collecting QoE measurements per MBS service area and MBS session ID (R3-232079; contact: Huawei) |
RAN3 |
| R2-2304658 |
Reply LS on buffer level threshold-based RVQoE reporting (S4-230684; contact: Apple) |
SA4 |
| R2-2305381 |
Running CR for QoE measurements |
Ericsson |
| R2-2306476 |
Revised Work Plan for Rel-18 NR QoE Enhancement |
China Unicom |
| 7.14.2 |
QoE measurements in RRC_IDLE INACTIVE |
|
| R2-2305076 |
QoE Measurements in IDLE/INACTIVE States |
Apple |
| R2-2305138 |
Discussion on support of QoE measurements in RRC_IDLE and RRC_INACTIVE |
Lenovo |
| R2-2305310 |
Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE |
Samsung |
| R2-2305382 |
QoE measurements in RRC_INACTIVE and RRC_IDLE |
Ericsson |
| R2-2305606 |
Consideration on QoE measurement in RRC_IDLE/INACTIVE |
CMCC |
| R2-2305755 |
QoE measurements support in RRC IDLE and INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2305766 |
Open issues on QoE collection for IDLE and Inactive state |
Qualcomm Incorporated |
| R2-2305809 |
Discussion on QoE measurements for MBS broadcast services |
Huawei, HiSilicon |
| R2-2306107 |
Considerations on QoE measurement in IDLE and INACTIVE |
ZTE Corporation, Sanechips |
| R2-2306396 |
Discussion on QoE measurements in RRC IDLE and INACTIVE state |
CATT |
| R2-2306478 |
Discussion on QoE measurements in RRC_IDLE and INACTIVE states |
China Unicom |
| R2-2306561 |
LS on area scope for QoE measurements |
Samsung |
| R2-2306569 |
LS on area scope for QoE measurements |
RAN2 |
| 7.14.3 |
Rel-17 leftover topics for QoE |
|
| R2-2305015 |
Application Layer Measurement Reporting for unlicensed spectrum |
Samsung Electronics Co., Ltd |
| R2-2305077 |
[DRAFT] Reply LS on assistance information for handling of QoE reporting upon RAN
overload |
Apple |
| R2-2305139 |
Discussion on Rel-17 leftover topics for QoE |
Lenovo |
| R2-2305362 |
Discussion on Rel-17 leftover issues for QoE |
NEC |
| R2-2305384 |
Event based RVQoE reporting |
Ericsson |
| R2-2305756 |
Discussion on Rel-17 leftovers |
Nokia, Nokia Shanghai Bell |
| R2-2305811 |
Discussion on Rel-17 left-over issues |
Huawei, HiSilicon |
| R2-2306109 |
Considerations on Rel-17 leftover issues for QoE |
ZTE Corporation, Sanechips |
| R2-2306397 |
Discussion on Rel-17 leftover topics for QoE |
CATT |
| 7.14.4 |
Support of QoE measurements for NR-DC |
|
| R2-2305078 |
Discussions on QoE Reporting for NR-DC |
Apple |
| R2-2305311 |
Discussion on QoE measurement for NR-DC |
Samsung |
| R2-2305383 |
QoE measurements in NR-DC |
Ericsson |
| R2-2305479 |
Support of QoE measurements for NR-DC |
LG Electronics Inc. |
| R2-2305607 |
Consideration on QoE measurement for NR-DC |
CMCC |
| R2-2305757 |
Detailed handling of QoE configuration and reporting in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2305767 |
Open issues to support QoE collection in NR-DC |
Qualcomm Incorporated |
| R2-2305810 |
Discussion on QoE measurements in NR-DC |
Huawei, HiSilicon |
| R2-2306108 |
Considerations on QoE measurement for NR-DC |
ZTE Corporation, Sanechips |
| R2-2306398 |
Discussion on support of QoE measurement for NR-DC |
CATT |
| R2-2306477 |
Discussion on QoE configuration and reporting for NR-DC |
China Unicom |
| 7.15.1 |
Organizational |
|
| R2-2304618 |
LS on MCSt resource (re-)selection (R1-2304257; contact: OPPO) |
RAN1 |
| R2-2304665 |
Work plan of R18 SL-Evo |
OPPO, LG |
| R2-2305179 |
Stage 2 Running CR of TS 38.300 for SL Evolution |
InterDigital |
| R2-2306233 |
Discussion on R1 LS on MCSt |
OPPO |
| R2-2306711 |
Stage 2 Running CR of TS 38.300 for SL Evolution |
InterDigital |
| 7.15.2 |
SL-U: SL Consistent LBT failure, SL LCP |
|
| R2-2304666 |
Discussion on C-LBT and LCP Enhancement |
OPPO |
| R2-2304764 |
Discussion on shared COT and LCP |
vivo |
| R2-2304788 |
Discussion on SL consistent LBT failure and LCP impact |
LG Electronics Inc. |
| R2-2304805 |
Discussion on SL consistent LBT failure and LCP enhancement |
Huawei, HiSilicon |
| R2-2304831 |
Remaining issues on SL consistent LBT failure |
vivo |
| R2-2304934 |
Discussion on left issues for SL-U LBT |
SHARP Corporation |
| R2-2304975 |
Discussion on Sidelink consistent LBT failure and LCP |
ZTE Corporation, Sanechips |
| R2-2305027 |
Remaining issues on consistent LBT failure |
Ericsson |
| R2-2305089 |
Discussion on SL LCP and consistent LBT failure recovery |
Apple |
| R2-2305173 |
LBT Failure for SL Unlicensed |
InterDigital |
| R2-2305174 |
Implementing LCP for SL Unlicensed |
InterDigital |
| R2-2305227 |
Discussion on SL consistent LBT failure |
Xiaomi |
| R2-2305228 |
Discussion on LCP restriction from COT sharing |
Xiaomi |
| R2-2305283 |
Further Discussion on SL LBT and LCP |
CATT |
| R2-2305357 |
Further dicsussion on SL consistent LBT failure |
NEC |
| R2-2305554 |
Discussion on aspects related to consistent LBT failure and COT sharing |
Spreadtrum Communications |
| R2-2305734 |
Remaining details of SL LCP and SL consistent LBT procedure |
Lenovo |
| R2-2305924 |
On recovery of Consistent LBT failure |
Nokia, Nokia Shanghai Bell |
| R2-2305931 |
R2-23xxxxx On the applicability of enhanced LCP |
Nokia, Nokia Shanghai Bell |
| R2-2305946 |
On SL-U LBT failure |
Intel Corporation |
| R2-2305949 |
On Shared COT and Enhanced SL LCP |
Intel Corporation |
| R2-2306055 |
Discussion on SL C-LBT failure and SL LCP |
Qualcomm India Pvt Ltd |
| R2-2306386 |
Discussion on SL Consistent LBT failure |
ITL |
| R2-2306519 |
SL C-LBT Failure recovery |
Samsung |
| R2-2306713 |
LS on C-LBT Failure Recovery |
RAN2 |
| 7.15.3 |
SL-U: SL resource (re)selection, MCSt impacts |
|
| R2-2304667 |
Discussion on Resource (Re)selection |
OPPO |
| R2-2304683 |
Consideration on MCSt impact |
NEC |
| R2-2304684 |
SL resource (re)selection |
NEC |
| R2-2304793 |
Discussion on SL resource (re)selection and MCSt impact |
LG Electronics Inc. |
| R2-2304806 |
Consideration on SL resource (re)selection and MCSt |
Huawei, HiSilicon |
| R2-2304976 |
Discussion on SL resource (re)selection for SL-U |
ZTE Corporation, Sanechips |
| R2-2305028 |
Resource selection and reselection for SL-U |
Ericsson |
| R2-2305090 |
Discussion on resource (re)selection and MCSt in SL-U |
Apple |
| R2-2305175 |
Mode 2 Resource Selection Considering LBT Impacts |
InterDigital |
| R2-2305176 |
Discussion on RAN1 LS on MCSt |
InterDigital |
| R2-2305177 |
Draft Response LS on MCSt resource (re)selection |
InterDigital |
| R2-2305229 |
Discussion on resource allocation for SL-U |
Xiaomi |
| R2-2305284 |
Discussion on MCSt |
CATT,GOHIGH |
| R2-2305686 |
Discussion on resource (re)selection for NR SL-U |
Lenovo |
| R2-2305923 |
On MCSt impacts on the resource selection procedure |
Nokia, Nokia Shanghai Bell |
| R2-2306256 |
Discussion on Multi-Consecutive Slots transmission |
vivo |
| R2-2306525 |
SL resource (re)selection |
Samsung |
| R2-2306714 |
[AT122][509][V2X/SL] Discussion on MCSt (OPPO) |
OPPO |
| R2-2306716 |
Reply LS on MCSt resource (re-)selection |
RAN2 |
| 7.15.4 |
SL-U: Others |
|
| R2-2304757 |
Discussion on the other remaining issues in SL-U |
OPPO |
| R2-2304794 |
Discussion on SL-U others |
LG Electronics Inc. |
| R2-2304807 |
Impact on SL CAPC and SL DRX |
Huawei, HiSilicon |
| R2-2304977 |
Discussion on SL CAPC and SL CG |
ZTE Corporation, Sanechips |
| R2-2305030 |
Other aspects on SL-U |
Ericsson |
| R2-2305091 |
Discussion on remaining issues on CAPC and SL DRX in SL-U |
Apple |
| R2-2305230 |
Discussion on other aspects for SL-U |
Xiaomi |
| R2-2305285 |
Consideration on CAPC and LBT impacts |
CATT |
| R2-2305687 |
Other remaining issue for NR SL-U |
Lenovo |
| R2-2305947 |
Discussion on SL-U open aspects |
Intel Corporation |
| R2-2306384 |
Discussion on SL DRX in SL-U |
ITL |
| R2-2306523 |
Remaining issues |
Samsung |
| 7.15.5 |
SL-FR2 |
|
| R2-2304685 |
Sidelink Operation on FR2 |
NEC |
| R2-2304718 |
Discussion on SL-FR2 aspects in RAN2 |
Nokia, Nokia Shanghai Bell |
| R2-2304758 |
Discussion on SL-FR2 impact |
OPPO |
| R2-2304765 |
Discussion on FR2 |
vivo |
| R2-2304796 |
Discussion on RAN2 aspects of SL-FR2 |
LG Electronics Inc. |
| R2-2304847 |
Discussion on SL-FR2 |
Huawei, HiSilicon |
| R2-2304978 |
Discussion on sidelink FR2 |
ZTE Corporation, Sanechips |
| R2-2305029 |
SL in FR2 |
Ericsson |
| R2-2305092 |
Discussion on RAN2 aspects of SL FR2 |
Apple |
| R2-2305220 |
Discussion on SL-FR2 impact to RAN2 |
Xiaomi |
| R2-2305236 |
Discussion on sidelink operation on FR2 licensed spectrum |
China Telecom |
| R2-2305286 |
Discussion on Sidelink Operation on FR2 |
CATT |
| R2-2305688 |
Discussion on FR2 operation for NR SL |
Lenovo |
| R2-2306056 |
Discuss on SL-FR2 |
Qualcomm India Pvt Ltd |
| R2-2306472 |
RAN2 Aspects of NR Sidelink Operation in FR2 |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2306522 |
SL-FR2 |
Samsung |
| 7.15.6 |
SL-CA |
|
| R2-2304668 |
Discussion on Carrier Aggregation |
OPPO |
| R2-2304686 |
Sidelink CA operation |
NEC |
| R2-2304798 |
Discussion on remaining issues of SL-CA enhancements |
LG Electronics Inc. |
| R2-2304832 |
Further discussion on the support of CA for NR Sidelink Mode-2 |
vivo |
| R2-2304848 |
Discussion on SL CA operation |
Huawei, HiSilicon |
| R2-2304979 |
Discussion on sidelink CA |
ZTE Corporation, Sanechips |
| R2-2305031 |
Aspects of SL CA |
Ericsson |
| R2-2305093 |
Discussion on Sidelink CA |
Apple |
| R2-2305178 |
Carrier Aggregation for NR SL |
InterDigital |
| R2-2305231 |
Discussion on carrier aggregation for NR sidelink |
Xiaomi |
| R2-2305287 |
Discussion on NR sidelink CA |
CATT |
| R2-2305358 |
Discussion on carrier selection for SL CA |
NEC |
| R2-2305689 |
Discussion on multi-carrier operation for NR SL |
Lenovo |
| R2-2305948 |
Discussion on NR SL Carrier Aggregation |
Intel Corporation |
| R2-2306057 |
Discussion on SL CA |
Qualcomm India Pvt Ltd |
| R2-2306315 |
On support of Sidelink CA in NR |
Nokia, Nokia Shanghai Bell |
| R2-2306471 |
RAN2 Aspects of NR Sidelink Carrier Aggregation |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2306518 |
SL CA for unicast |
Samsung |
| R2-2306715 |
Summary of offline discussion on TX profile in NR SL CA |
Apple (Rapporteur) |
| 7.15.7 |
SL-Co-Ex |
|
| R2-2304669 |
Discussion on LTE-V2x and NR-V2x Co-Existence |
OPPO |
| R2-2304830 |
Discussion on RAN2 impact on LTE sidelink and NR sidelink co-existence |
vivo |
| R2-2304849 |
Support of co-channel coexitence for LTE SL and NR SL |
Huawei, HiSilicon |
| R2-2304980 |
Discussion on Co-channel coexistence for LTE sidelink and NR sidelink |
ZTE Corporation, Sanechips |
| R2-2305032 |
Discussion and LTE and NR coexistence |
Ericsson |
| R2-2305094 |
Discussion on resource selection in co-channel existence |
Apple |
| R2-2305288 |
Discussion on Coexistence for LTE sidelink and NR sidelink |
CATT |
| R2-2305690 |
Discussion on co-channel coexistence for LTE and NR SL |
Lenovo |
| R2-2305825 |
Identified issues for Sidelink Coexistence |
Nokia, Nokia Shanghai Bell |
| R2-2306058 |
Discussion on SL Co-existence |
Qualcomm India Pvt Ltd |
| R2-2306521 |
SL Co-Ex |
Samsung |
| R2-2306712 |
Summary of [AT122][507][V2X/SL] Any essential stage-2 RAN2 work for sL Co-Ex (OPPO) |
OPPO |
| 7.16.1 |
Organizational |
|
| R2-2306437 |
Progress and Next Steps: Rapporteur's Insights |
Ericsson, Qualcomm Incorporated |
| 7.16.2.1 |
Architecture and General |
|
| R2-2304660 |
Discussion on Model ID and Model Meta Data |
OPPO |
| R2-2304661 |
Functionality Mapping for LCM Purposes |
OPPO |
| R2-2304676 |
General aspects of AIML framework |
NEC |
| R2-2304945 |
Further discussions on architecture general aspects of AIML for NR air-interface |
CATT, Turkcell |
| R2-2304959 |
Discussions on Model-ID and Functionality-ID based LCM |
Fujitsu |
| R2-2304990 |
Architecture and general for AIML |
MediaTek Inc. |
| R2-2305085 |
Further discussion on model ID and AI/ML architecture |
Apple |
| R2-2305145 |
AI/ML Architecture |
Nokia, Nokia Shanghai Bell |
| R2-2305162 |
UE capability reporting and model ID |
InterDigital |
| R2-2305221 |
Discussion on architecture aspects |
Xiaomi |
| R2-2305327 |
Discussion on Architecture General |
vivo |
| R2-2305448 |
Model ID, AIML related capability and functionality mapping |
Intel Corporation |
| R2-2305567 |
Discussion on general AI architecture |
Spreadtrum Communications |
| R2-2305570 |
Discussion on other model control method |
Spreadtrum Communications |
| R2-2305613 |
Discussion on general architecture for AIML for NR air interface |
CMCC |
| R2-2305680 |
Discussion on AI framework and functionality mapping |
Lenovo |
| R2-2305681 |
Discussion on identifier used for UE side/part model LCM |
Lenovo |
| R2-2305788 |
AI/ML functionality and model-ID based LCM procedure |
Samsung Shenzhen |
| R2-2305824 |
Discussion on AI/ML Capability Reporting and Model LCM |
SHARP Corporation |
| R2-2305969 |
Discussion on AI/ML Architecture General |
Qualcomm Incorporated |
| R2-2306045 |
Discussion on the architectural and general aspects of AI/ML |
Futurewei Technologies |
| R2-2306092 |
Discussion on architecture and general |
Huawei, HiSilicon |
| R2-2306268 |
Architecture and LCM aspects of AI/ML for NR air interface |
AT&T |
| R2-2306285 |
AIML method_Architecture General |
LG Electronics |
| R2-2306411 |
Discussion on Architecture and General |
TCL Communication Ltd. |
| R2-2306414 |
Discussion on Functionality Mapping within NW |
ZTE Corporation, Sanechips |
| R2-2306438 |
Architecture and management for AIML |
Ericsson |
| R2-2306440 |
Applicability reporting |
Ericsson |
| 7.16.2.2 |
Data Collection |
|
| R2-2304662 |
Data Collection for LCM Purposes |
OPPO |
| R2-2304677 |
AIML Data Collection |
NEC |
| R2-2304946 |
Considerations on data collection of AIML for NR air-interface |
CATT, Turkcell |
| R2-2304960 |
Discussions on AIML data collection |
Fujitsu |
| R2-2305086 |
Further discussion on data collection for AI/ML |
Apple |
| R2-2305146 |
AI/ML Data collection |
Nokia, Nokia Shanghai Bell |
| R2-2305222 |
Discussion on data collection |
Xiaomi |
| R2-2305308 |
Discussion on Data Collection |
MediaTek Inc. |
| R2-2305328 |
Discussion on data collection |
vivo |
| R2-2305449 |
Further analysis on data collection framework |
Intel Corporation |
| R2-2305525 |
Some considerations about data collection |
Sony |
| R2-2305568 |
Discussion on data collection |
Spreadtrum Communications |
| R2-2305614 |
Discussion on data collection for AIML model |
CMCC |
| R2-2305682 |
Qualitative analysis on data collection requirements |
Lenovo |
| R2-2305792 |
Enhancements for RRM/MDT to support AI/ML data collection |
Samsung Shenzhen |
| R2-2305814 |
Data collection for AIML |
Interdigital Inc. |
| R2-2305970 |
Discussion on Data Collection Requirements/Constraints for Different LCM Purposes |
Qualcomm Incorporated |
| R2-2306093 |
Discussion on data collection |
Huawei, HiSilicon |
| R2-2306269 |
Data collection aspects of AI/ML for NR air interface |
AT&T |
| R2-2306286 |
AIML method_Data Collection |
LG Electronics |
| R2-2306408 |
Data collection for AIML methods |
TCL Communication Ltd. |
| R2-2306415 |
Further Discussion On the Purpose Driven Data Collection in LCM |
ZTE Corporation, Sanechips |
| R2-2306451 |
Data collection for AI/ML |
Ericsson |
| R2-2306783 |
Report of [AT122][001][AIML18] LS out on Data Collection Requirements and Assumptions (vivo) |
vivo |
| R2-2306784 |
[DRAFT] LS out on Data Collection Requirements and Assumptions |
vivo |
| R2-2306833 |
[DRAFT] LS out on Data Collection Requirements and Assumptions |
vivo |
| R2-2306906 |
LS out on Data Collection Requirements and Assumptions |
RAN2 |
| 7.16.2.3 |
Model transfer – delivery |
|
| R2-2304663 |
Open Issue Discussion on Model Transfer/Delivery |
OPPO |
| R2-2304678 |
AIML Model transfer |
NEC |
| R2-2304679 |
AIML Model transfer for mobility |
NEC |
| R2-2304863 |
AI/ML model delivery/transfer on CP RRC |
Dell Technologies |
| R2-2304947 |
Further discussions on AIML model transfer |
CATT, Turkcell |
| R2-2304961 |
Discussions on AIML model transfer via air interface |
Fujitsu |
| R2-2305087 |
Further discussion on model transfer |
Apple |
| R2-2305147 |
AI/ML Model transfer / delivery |
Nokia, Nokia Shanghai Bell |
| R2-2305223 |
Discussion on model delivery |
Xiaomi |
| R2-2305309 |
Discussion on AI/ML Model Transfer/Delivery |
MediaTek Inc. |
| R2-2305329 |
Discussion on model transfer |
vivo |
| R2-2305450 |
architecture impact on model transfer method |
Intel Corporation |
| R2-2305569 |
Discussion on model transfer-delivery |
Spreadtrum Communications |
| R2-2305615 |
Discussion on AIML model transfer delivery |
CMCC |
| R2-2305683 |
Discussion on gNB/LMF awareness of UE side model |
Lenovo |
| R2-2305787 |
Discussion on model transfer/delivery solutions |
Samsung Shenzhen |
| R2-2305815 |
Way forward for AIML Model transfer/delivery |
Interdigital Inc. |
| R2-2305971 |
Discussion on Model Transfer/Delivery |
Discussion and Decision |
| R2-2306094 |
Discussion on model transfer and model delivery |
Huawei, HiSilicon |
| R2-2306270 |
AI/ML model transfer and delivery |
AT&T |
| R2-2306287 |
AIML method_Model Transfer Delivery |
LG Electronics |
| R2-2306416 |
urther Considerations On the Model Transfer study in RAN2 |
ZTE Corporation, Sanechips |
| R2-2306439 |
On the need for model transfer |
Ericsson |
| 7.16.2.4 |
Model Control other |
|
| R2-2304948 |
Considerations on other model control procedures |
CATT, Turkcell |
| R2-2304965 |
AI ML model management across RRC state transitions and mobility among non-interoperable networks |
Rakuten Symphony |
| R2-2305088 |
Discussion on UE capability reporting and LCM |
Apple |
| R2-2305148 |
AI/ML Control and other topics |
Nokia, Nokia Shanghai Bell |
| R2-2305163 |
Decision and Signaling for AI/ML Model Switching |
InterDigital |
| R2-2305314 |
Model Control and Model Monitoring |
MediaTek Inc. |
| R2-2305330 |
Discussion on model management and identification |
vivo |
| R2-2305451 |
model control procedure: RAN2 impact |
Intel Corporation |
| R2-2305526 |
Some considerations about CSI compression |
Sony |
| R2-2305646 |
Model ID across non-interoperable networks |
Rakuten Symphony |
| R2-2305677 |
AI/ML model control for positioning accuracy enhancement |
Xiaomi |
| R2-2305789 |
Indication of supported AI/ML models and functionalities |
Samsung Shenzhen |
| R2-2305826 |
Discussion on Model Monitoring and Reporting Considering Functionality and Model ID based LCM |
SHARP Corporation |
| R2-2305973 |
Discussion on Life Cycle Management |
Qualcomm Incorporated |
| R2-2306095 |
Discussion on model control and others |
Huawei, HiSilicon |
| R2-2306271 |
AI/ML model control |
AT&T |
| R2-2306417 |
Consideration on General Porocedure For Different Use Cases |
ZTE Corporation, Sanechips |
| 7.17 |
Dual Transmission/Reception (Tx/Rx) Multi-SIM for NR |
|
| R2-2306953 |
Running RRC CR for NR MUSIM enhancements |
vivo |
| R2-2306968 |
38.300 Running Stage-2 CR for NR MUSIM enhancements |
China Telecom |
| 7.18.1 |
Organizational |
|
| R2-2304795 |
Draft running CR for MAC spec for MT-SDT |
Huawei, HiSilicon |
| R2-2305022 |
Introduction of MT-SDT (RRC Running CR) |
ZTE Corporation (rapporteur) |
| R2-2305750 |
Introduction of MT-SDT in Stage-2 |
Nokia, Nokia Shanghai Bell |
| R2-2306958 |
Summary for [Post122][309][MT-SDT] 38.321 Running CR (Huawei) |
Huawei, HiSilicon |
| R2-2306963 |
Introduction of MT-SDT in Stage-2 |
Nokia, Nokia Shanghai Bell |
| R2-2306965 |
Introduction of MT-SDT to MAC spec |
Huawei, HiSilicon |
| 7.18.2 |
Control plane aspects |
|
| R2-2304706 |
Discussion on Supporting MT-SDT from CP Perspective |
vivo Mobile Com. (Chongqing) |
| R2-2304725 |
Control plane aspects of MT SDT Procedure in RRC_INACTIVE state |
Samsung Electronics Co., Ltd |
| R2-2304935 |
Discussion on subsequent transmission within MT-SDT |
SHARP Corporation |
| R2-2305021 |
MT-SDT Control plane open isssues |
ZTE Corporation, Sanechips |
| R2-2305299 |
Discussion on control plane issues for MT-SDT |
OPPO |
| R2-2305352 |
Further MT-SDT discussion |
Ericsson |
| R2-2305491 |
MT SDT mechanism (including configuration, paging, resume and capabilities) |
Intel Corporation |
| R2-2305527 |
Remaining procedures for MT-SDT |
Sony |
| R2-2305583 |
Discussion on the configuration of MT-SDT |
Xiaomi |
| R2-2305735 |
Discussion on remaining CP issues for MT-SDT |
Lenovo |
| R2-2305791 |
Control plane aspects of MT-SDT |
Qualcomm Incorporated |
| R2-2305806 |
Control plane aspects of MT-SDT |
Huawei, HiSilicon |
| R2-2305906 |
CP aspects for MT-SDT procedure |
Nokia, Nokia Shanghai Bell |
| R2-2306128 |
Discussion on DL SPS for MT-SDT |
ASUSTeK |
| R2-2306141 |
Support of SPS in MT-SDT |
LG Electronics Inc. |
| R2-2306160 |
Discussion on MT-SDT |
Apple |
| R2-2306341 |
Consideration on CP common aspects of MT-SDT |
China Telecom Corporation Ltd. |
| R2-2306399 |
Consideration on CP aspects for MT-SDT |
CATT |
| 7.18.3 |
User plane aspects |
|
| R2-2304707 |
Discussion on Supporting MT-SDT from UP Perspective |
vivo Mobile Com. (Chongqing) |
| R2-2304726 |
User plane aspects of MT SDT Procedure in RRC_INACTIVE state |
Samsung Electronics Co., Ltd |
| R2-2305023 |
MT-SDT user plane open isssues |
ZTE Corporation, Sanechips |
| R2-2305300 |
Discussion on user plane issues for MT-SDT |
OPPO |
| R2-2305353 |
Handling BWP restrictions in MT-SDT |
Ericsson |
| R2-2305557 |
Discussion on MT-SDT procedure |
Spreadtrum Communications |
| R2-2305595 |
Discussion on MT-SDT procedure |
Continental Automotive |
| R2-2305736 |
Discussion on remaining UP issues for MT-SDT |
Lenovo |
| R2-2305751 |
MT-SDT UP impacts |
Nokia, Nokia Shanghai Bell |
| R2-2305793 |
User plane aspects of MT-SDT |
Qualcomm Incorporated |
| R2-2305805 |
User plane aspects of MT-SDT |
Huawei, HiSilicon |
| R2-2305807 |
SPS support for MT-SDT |
Huawei, HiSilicon, Xiaomi, vivo, LGE, CMCC |
| R2-2305953 |
MT SDT mechanism (including CG and ROHC) |
Intel Corporation |
| R2-2306142 |
Discussion on MT-SDT procedure |
LG Electronics Inc. |
| R2-2306342 |
Consideration on UP common aspects of MT-SDT |
China Telecom Corporation Ltd. |
| R2-2306379 |
Handling BWP restrictions in MT-SDT |
Ericsson |
| R2-2306400 |
Consideration on UP aspects for MT-SDT |
CATT |
| R2-2306527 |
On support of DL SPS |
MediaTek Inc. |
| 7.19.1 |
Organizational |
|
| R2-2304619 |
LS on Msg4 PDSCH transmission to Rel-18 eRedCap UEs (R1-2304262; contact: Ericsson) |
RAN1 |
| R2-2304624 |
RAN3 progress on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 (R3-231951; contact: Ericsson) |
RAN3 |
| R2-2304648 |
Reply LS on Paging Policy Information for Network Triggered Connection Resume (S2-2305617; contact: Ericsson) |
SA2 |
| R2-2304649 |
Reply LS on INACTIVE eDRX above 10.24sec and SDT (S2-2305619; contact: Intel) |
SA2 |
| R2-2305004 |
How to capture “eRedCap UE” in the running CRs/Rel-18 specifications |
Huawei, HiSilicon |
| R2-2305011 |
Running MAC CR for eRedCap |
vivo (Rapporteur) |
| R2-2305377 |
Running CR for TS 38.300 for Rel-18 eRedCap |
OPPO |
| R2-2305471 |
Running 38.304 CR for enhanced support of reduced capability NR devices |
Huawei, HiSilicon |
| R2-2306039 |
38.306 UE capability for Rel-18 eRedCap |
Intel Corporation |
| R2-2306040 |
38.331 UE capability for Rel-18 eRedCap |
Intel Corporation |
| R2-2306223 |
Introduction of eRedCap in 38331 |
Ericsson |
| R2-2306733 |
Running CR for TS 38.300 for Rel-18 eRedCap |
OPPO |
| R2-2306734 |
Running 38.304 CR for enhanced support of reduced capability NR devices |
Huawei, HiSilicon |
| R2-2306735 |
38.306 UE capability for Rel-18 eRedCap |
Intel Corporation |
| R2-2306736 |
38.331 UE capability for Rel-18 eRedCap |
Intel Corporation |
| R2-2306737 |
Running MAC CR for eRedCap |
vivo (Rapporteur) |
| R2-2306738 |
Introduction of eRedCap in 38331 |
Ericsson |
| R2-2306969 |
Introduction of eRedCap in 38331 |
Ericsson |
| 7.19.2 |
Enhanced eDRX in RRC_INACTIVE |
|
| R2-2304682 |
Fallback behaviour for eRedcap UE |
NEC |
| R2-2304738 |
Discussion on enhanced eDRX in RRC_INACTIVE |
OPPO |
| R2-2304901 |
Discussion on enhanced eDRX in RRC_INACTIVE |
CATT, CEPRI |
| R2-2304920 |
Remaining issues on Enhanced eDRX for eRedCap |
vivo, Guangdong Genius |
| R2-2304996 |
Discussion on e-DRX for eRedcap Devices |
Xiaomi Communications |
| R2-2305312 |
Discussion on enhanced eDRX in RRC_INACTIVE |
Samsung |
| R2-2305436 |
Further impacts to support eDRX in RRC_INACTIVE above 10.24 sec |
Intel Corporation |
| R2-2305472 |
Discussion on enhanced eDRX in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2305622 |
Discussion on eDRX in RRC_INACTIVE |
CMCC |
| R2-2305794 |
Discussion on enhanced eDRX in RRC inactive |
Qualcomm Incorporated |
| R2-2305900 |
Remaining issues for enhanced eDRX in RRC_INACTIVE |
MediaTek Inc. |
| R2-2305905 |
On eDRX for enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| R2-2305962 |
Remaining issues of enhanced eDRX in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2306228 |
Extended eDRX cycles in RRC_INACTIVE |
Ericsson |
| R2-2306528 |
Extended eDRX cycles in RRC_INACTIVE |
Ericsson |
| 7.19.3 |
Further reduced UE complexity in FR1 |
|
| R2-2304722 |
Potential impacts to random access for Rel-18 eRedCap Ues |
Samsung Electronics Co., Ltd |
| R2-2304739 |
Discussion on early indication for eRedCap UE |
OPPO |
| R2-2304752 |
Discussion on cellbarring for eRedCap UEs |
OPPO |
| R2-2304902 |
Discussion on further UE complexity reduction |
CATT, CEPRI |
| R2-2304905 |
[Draft] Reply LS on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
CATT |
| R2-2304921 |
Discussion on access restriction for eRedCap |
vivo, Guangdong Genius |
| R2-2304922 |
Discussion on capability for eRedCap |
vivo, Guangdong Genius |
| R2-2304997 |
Discussion on early indication for eRedcap devices |
Xiaomi Communications |
| R2-2304998 |
Discussion on UE access restrictions and other impacts for eRedcap devices |
Xiaomi Communications |
| R2-2305003 |
eRedCap access restriction and the issue in RAN1 LS |
Huawei, HiSilicon |
| R2-2305098 |
Early identification of eRedCap UE at RACH |
Apple |
| R2-2305099 |
R17 RedCap support of R18 eRedCap supporting gNBs |
Apple |
| R2-2305313 |
Discussion on further reduced UE complexity in FR1 |
Samsung |
| R2-2305359 |
Discussion on Msg4 PDSCH transmission to Rel-18 eRedCap UE |
NEC |
| R2-2305360 |
Further discussion on access restriction for eRedCap |
NEC |
| R2-2305437 |
Capability impacts for Rel-18 eRedCap UEs |
Intel Corporation |
| R2-2305558 |
Discussion on further reduced UE complexity in FR1 for eRedCap UE |
Spreadtrum Communications |
| R2-2305623 |
Discussion on further reduced UE complexity |
CMCC |
| R2-2305796 |
Discussion on further complexity reduction for eRedCap UE |
Qualcomm Incorporated |
| R2-2305797 |
Discussion on optional UE capability filter for eRedCap UE |
Qualcomm Incorporated, Ericsson, Intel |
| R2-2305869 |
Access restrictions for eRedCap UE |
Sierra Wireless. S.A. |
| R2-2305901 |
Open aspects of initial access for eRedCap UEs |
MediaTek Inc. |
| R2-2305904 |
On access restrictions for enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| R2-2305932 |
Considerations on Further reduced UE complexity for eRedcap |
Sequans Communications |
| R2-2305963 |
Early indication and access restriction for eRedCap UE |
ZTE Corporation, Sanechips |
| R2-2305964 |
Capability definition and report for eRedCap UE |
ZTE Corporation, Sanechips |
| R2-2306224 |
Discussion on Msg4 PDSCH transmission to Rel-18 eRedCap UEs |
Ericsson |
| R2-2306234 |
Early indication and access control for BB BW reduced UEs |
Ericsson |
| R2-2306237 |
Access restriction and capabilities for eRedCap UEs |
Ericsson |
| R2-2306314 |
On Msg4 with larger number of PRBs |
Nokia, Nokia Shanghai Bell |
| R2-2306332 |
Discussion on Cell barring for eRedCap |
NTT DOCOMO INC. |
| R2-2306348 |
Remaining issues on early indication for Rel-18 eRedCap UE |
LG Electronics Inc. |
| R2-2306426 |
Further discussions on access restriction for eRedCap |
Futurewei |
| R2-2306524 |
Access restriction and capabilities for eRedCap UEs |
Ericsson |
| R2-2306731 |
Summary of the offline on R18 eRedCap UEs access restrictions |
ZTE Corporation, Sanechips |
| 7.20.2 |
Two TAs for multi-DCI multi-TRP |
|
| R2-2304766 |
Discussion on multiple TAG |
OPPO |
| R2-2304938 |
Further issues for Multi-TRP with two TAs support |
SHARP Corporation |
| R2-2305318 |
Discussions on Two TAs for Multi-DCI Multi-TRP |
CATT |
| R2-2305588 |
Discussion on Two TAs for Multi-TRP |
NEC Corporation |
| R2-2305719 |
Discussion on the impacts of Two TAs for multi-DCI multi-TRP operation |
Lenovo |
| R2-2305720 |
Discussion on the UE-initiated RACH procedure in multi-TRP operation |
Lenovo |
| R2-2305752 |
RA procedure while SpCell is configured with 2 TAGs |
Nokia, Nokia Shanghai Bell |
| R2-2305799 |
Discussion on multi-DCI multi-TRP with two TAs |
Qualcomm Incorporated |
| R2-2305848 |
On 2TA operation |
Ericsson |
| R2-2305921 |
Two TAs for multi-DCI multi-TRP |
Huawei, HiSilicon |
| R2-2306036 |
On 2TA operation |
Ericsson |
| R2-2306140 |
Discussion on TA maintenance in two TAs for multi-TRP |
LG Electronics Inc. |
| R2-2306161 |
Support of Two TAs for multi-DCI multi-TRP |
Apple |
| R2-2306327 |
Discussion on two TAs for multi-DCI multi-TRP |
Samsung Research America |
| R2-2306421 |
Further Considerations On UE initiated RACH for acquiring TA |
ZTE Corporation,Sanechips |
| R2-2306433 |
Status of open issues on Two TAs for mDCI mTRP |
NTT DOCOMO INC. |
| 7.20.3 |
Other |
|
| R2-2304767 |
Discussion on MAC CE design for mTRP |
OPPO |
| R2-2304876 |
RAN2 impacts of multi-TRP with unified TCI states |
Nokia, Nokia Shanghai Bell |
| R2-2305319 |
Discussion on Unified TCI Framework Extension for Multi-TRP |
CATT |
| R2-2305800 |
Discussion on unified TCI framework extension for mTRP operation |
Qualcomm Incorporated |
| R2-2305851 |
On unified TCI for mTRP |
Ericsson |
| R2-2305922 |
Extension of unified TCI framework for mTRP |
Huawei, HiSilicon |
| R2-2306129 |
Intra-UE prioritization for Simultaneous multi-panel transmission |
ASUSTeK |
| R2-2306144 |
Discussion on impact of multi-TRP on MAC CE |
LG Electronics Inc. |
| R2-2306225 |
Remaining issues on unified TCI extension to mTRP operation |
Samsung |
| R2-2306420 |
Considerations on unified TCI state extension for s-DCI based mTRP |
ZTE Corporation,Sanechips |
| R2-2306532 |
Considerations on unified TCI state extension for s-DCI based mTRP |
ZTE Corporation, Sanechips |
| 7.21.1 |
Organizational |
|
| R2-2304613 |
LS on PRACH coverage enhancement (R1-2304141; contact: China Telecom) |
RAN1 |
| 7.21.2 |
Control plane issues |
|
| R2-2304702 |
RAN2 Impacts of Multiple PRACH Transmissions from CP |
vivo Mobile Com. (Chongqing) |
| R2-2304723 |
Control plane aspects of further NR Coverage Enhancements |
Samsung Electronics Co., Ltd |
| R2-2304903 |
Discussion on CP issues for MSG1 repetition |
CATT |
| R2-2305127 |
UL Coverage Enhancements Control Plane |
Qualcomm Incorporated |
| R2-2305237 |
RACH partition framework of Coverage Enhancement |
China Telecom |
| R2-2305355 |
Discussion on Multiple PRACH Transmission Configuration |
Ericsson |
| R2-2305403 |
CP issues for PRACH coverage enhancement |
ZTE Corporation, Sanechips |
| R2-2305732 |
Discussion on RAN2 impact of PRACH enhancement |
Xiaomi |
| R2-2305929 |
Multiple PRACH transmissions – CP aspects |
InterDigital |
| R2-2306231 |
RRC aspects for Msg1 repetition |
Huawei, HiSilicon |
| R2-2306349 |
Signalling aspects on support of PRACH repetition |
LG Electronics Inc. |
| 7.21.3 |
User plane issues |
|
| R2-2304703 |
RAN2 Impacts of Multiple PRACH Transmissions from UP |
vivo Mobile Com. (Chongqing) |
| R2-2304724 |
User plane aspects of further NR Coverage Enhancements |
Samsung Electronics Co., Ltd |
| R2-2304904 |
Discussion on UP issues for MSG1 repetition |
CATT |
| R2-2305128 |
UL Coverage Enhancements User Plane |
Qualcomm Incorporated |
| R2-2305269 |
UP Impacts for Further NR Coverage Enhancements |
NEC Corporation |
| R2-2305354 |
Discussion on Multiple PRACH Transmission Procedures |
Ericsson |
| R2-2305404 |
UP issues for PRACH coverage enhancement |
ZTE Corporation, Sanechips |
| R2-2305753 |
UP impacts of PRACH CE |
Nokia, Nokia Shanghai Bell |
| R2-2305754 |
Fallback cases for PRACH repetition |
Nokia, Nokia Shanghai Bell |
| R2-2305930 |
Multiple PRACH transmissions – UP aspects |
InterDigital |
| R2-2306232 |
Discussion on MAC aspect with MSG1 repetition |
Huawei, HiSilicon |
| R2-2306350 |
RA procedure to support PRACH repetition |
LG Electronics Inc. |
| 7.22.1 |
Organizational |
|
| R2-2305745 |
Updated scope clarification of Rel-18 SI on LP-WUS/WUR |
vivo (Rapporteur) |
| R2-2305746 |
Work Plan for Rel-18 SI on LP-WUS/WUR |
vivo (Rapporteur) |
| R2-2305747 |
Update of TR 38.869 for LP-WUS WUR |
vivo (Rapporteur) |
| 7.22.2 |
Idle Inactive Mode |
|
| R2-2304714 |
Use of low-power receiver in RRC Idle/Inactive |
Qualcomm Incorporated |
| R2-2304748 |
Discussion on RRM measurement for LP-WUR |
OPPO |
| R2-2304923 |
Discussion on LP-WUS WUR in RRC idle/inactive |
vivo |
| R2-2304936 |
Discussion on LP-WUS in RRC_IDLE&INACTIVE state |
CATT |
| R2-2304988 |
Discussion on the considerations for LPWUS in RRC_IDLE INACTIVE |
NEC Corporation |
| R2-2305000 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2305528 |
Considerations on LP-WUR in RRC Idle/Inactive mode |
Sony |
| R2-2305903 |
LP-WUS in RRC IDLE and INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2305960 |
RAN2 impacts of LP-WUS in idle or inactive mode |
ZTE Corporation, Sanechips |
| R2-2306060 |
MR/LR UE behaviours for paging and mobility in RRC_IDLE/INACTIVE state |
Huawei, HiSilicon |
| R2-2306162 |
RAN2 impact on LP-WUS in IDLE/INACTIVE state |
Apple |
| R2-2306238 |
LP-WUS/WUR for RRC Idle and Inactive |
Ericsson |
| R2-2306482 |
On impact to IDLE/INACTIVE procedures to support LP-WUR |
SAMSUNG R&D INSTITUTE INDIA |
| 7.22.3 |
Connected Mode |
|
| R2-2304715 |
Use of low-power receiver in RRC Connected |
Qualcomm Incorporated |
| R2-2304750 |
Discussion on LP-WUR’s operation |
OPPO |
| R2-2304924 |
Discussion on LP-WUS WUR in RRC connected |
vivo |
| R2-2304937 |
Discussion on LP-WUS in RRC_CONNECTED state |
CATT |
| R2-2304989 |
Discussion on the considerations for LPWUS in RRC_CONNECTED |
NEC Corporation |
| R2-2304999 |
Discussing on LP-WUS monitoring for RRC_Connected |
Xiaomi Communications |
| R2-2305473 |
High layer procedures for LP-WUS in RRC_CONNECTED state |
Huawei, HiSilicon |
| R2-2305961 |
RAN2 impacts of LP-WUS in connected mode |
ZTE Corporation, Sanechips |
| R2-2306239 |
LP-WUS/WUR for RRC Connected |
Ericsson |
| R2-2306312 |
LP_WUS in RRC_CONNECTED |
Nokia, Nokia Shanghai Bell |
| R2-2306489 |
On impact to Connected mode procedures to support LP-WUR |
SAMSUNG R&D INSTITUTE INDIA |
| 7.23.1 |
Organizational |
|
| R2-2304605 |
Response to Reply LS on Proposed method for Time Synchronization status reporting to UE(s) (C1-232942; contact: Nokia) |
CT1 |
| R2-2304621 |
Reply LS on proposed method for time synchronization status reporting to UE(s) (R3-230811; contact: Nokia) |
RAN3 |
| R2-2305655 |
Stage 2 running CR on timing resiliency and URLLC |
Nokia, Nokia Shanghai Bell |
| 7.23.2 |
General |
|
| R2-2304704 |
Further Discussion on 5G Clock Quality Information Reporting |
vivo Mobile Com. (Chongqing) |
| R2-2304705 |
Discussion on RAN feedback for Upstream Scheduling |
vivo Mobile Com. (Chongqing) |
| R2-2304841 |
Discussion on TSS change notification procedure |
Huawei, HiSilicon |
| R2-2304842 |
Discussion on the update of event ID |
Huawei, HiSilicon |
| R2-2304972 |
RAN2 Impact of 5GS network timing synchronization status and reporting |
CATT |
| R2-2304973 |
Discussion on RAN feedback |
CATT |
| R2-2305079 |
RAN feedback for burst sending time adjustment |
Apple |
| R2-2305080 |
5GS Network Timing Synchronization in RRC_INACTIVE |
Apple |
| R2-2305129 |
Clock Quality Report Delivery |
Qualcomm Incorporated |
| R2-2305130 |
UL BAT Derivation at RAN |
Qualcomm Incorporated |
| R2-2305627 |
Discussion on the network timing synchronization status monitoring |
CMCC |
| R2-2305656 |
5GS network timing synchronization status and reporting |
Nokia, Nokia Shanghai Bell |
| R2-2305657 |
Reactive RAN feedback for upstream scheduling |
Nokia, Nokia Shanghai Bell |
| R2-2305738 |
Signaling of 5G Clock Quality Information |
Samsung |
| R2-2305739 |
Time Synchronization Status Update via EventID |
Samsung |
| R2-2305966 |
Further discussion on time synchronization status and reporting |
ZTE Corporation, Sanechips |
| R2-2305967 |
Discussion on the issue of RACH congestion |
ZTE Corporation, Sanechips |
| R2-2306343 |
Discussion on 5G network timing synchronization status and reporting |
China Telecom Corporation Ltd. |
| R2-2306464 |
Burst Arrival Time (BAT) offset derivation |
Ericsson |
| R2-2306473 |
Discussion on NR timing resiliency |
Ericsson |
| 7.24.1 |
TEI proposals by Other Groups |
|
| R2-2304609 |
LS on 1-symbol PRS (R1-2302201; contact: ZTE) |
RAN1 |
| R2-2304623 |
Reply LS on 1-symbol PRS (R3-231935; contact: ZTE) |
RAN3 |
| R2-2305769 |
CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] |
Ericsson |
| R2-2305770 |
CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] |
Ericsson |
| R2-2306079 |
Introduction of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2306080 |
Introduction of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2306081 |
Introduction of UE capability of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2306082 |
Introduction of UE capability of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2306083 |
Introduction of UE capability of 1-symbol PRS in 38.306[1symbol_PRS] |
ZTE Corporation |
| R2-2306770 |
CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] |
Ericsson |
| R2-2306773 |
CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] |
Ericsson |
| R2-2306793 |
Introduction of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2306794 |
Introduction of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2306795 |
Introduction of UE capability of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2306796 |
Introduction of UE capability of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2306797 |
Introduction of UE capability of 1-symbol PRS in 38.306[1symbol_PRS] |
ZTE Corporation |
| 7.24.2 |
TEI proposals by RAN2 |
|
| R2-2304759 |
Discussion on emergency cause value for SL Relay |
OPPO |
| R2-2304779 |
Open Issues on RedCap CFR for MBS Broadcast |
CATT, CBN |
| R2-2304822 |
Discussion on the CFR for Redcap UE |
Huawei, CBN, HiSilicon |
| R2-2304823 |
Correction on RRC for Redcap CFR |
Huawei, CBN, HiSilicon |
| R2-2304838 |
GNSS LOS/NLOS assistance information, stage 3 details and corrections |
Vodafone, Spirent, Ericsson, Telecom Italia |
| R2-2304877 |
Signalling overhead reduction of DC location reporting signalling [DCLoc-Overhead] |
Nokia, Nokia Shanghai Bell |
| R2-2304974 |
Discussion on MUSIM paging cause forwarding |
vivo |
| R2-2305014 |
Paging Cause forwarding |
Samsung Electronics Co., Ltd |
| R2-2305216 |
Discussion on how to support posSIB(s) forwarding |
Xiaomi |
| R2-2305265 |
Discussion on Yaw and APC enhancements |
Swift Navigation |
| R2-2305350 |
SDT Enhancements for Configured grants [SDT-Enh-CG] |
Ericsson, Intel Corporation, T-Mobile USA, ZTE Corporation |
| R2-2305427 |
Improvement of handling of timeConnFailure |
Nokia, Nokia Shanghai Bell |
| R2-2305474 |
GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia |
| R2-2305481 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia |
| R2-2305490 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia |
| R2-2305665 |
Correction options on RedCap MBS Broadcast reception in TEI18 |
ZTE, Sanechips |
| R2-2305774 |
Discussion on the issue of unpredictable measurement sequence for inter-frequency measurement reporting and specification impact |
CMCC, Ericsson, CATT |
| R2-2305850 |
Positioning and posSIB forwarding for remote UEs |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo |
| R2-2305852 |
Positioning restrictions for UE-to-network remote UEs [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2305854 |
Support positioning of L2 UE-to-network remote UEs [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2305857 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2305859 |
Capabilities of L2 UE-to-network relay UEs for positioning [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2305865 |
Downlink positioning performance results for remote UEs out of coverage |
MediaTek Inc. |
| R2-2305889 |
Support of Local Cartesian Coordinates in LPP |
Qualcomm Incorporated |
| R2-2305891 |
Support of Local Cartesian Coordinates in LPP [PosLocalCoords] |
Qualcomm Incorporated |
| R2-2305954 |
Discussion on Separate RedCap CFR for MBS Broadcast |
Qualcomm Incorporated, Ericsson, Verizon, FirstNet |
| R2-2305955 |
RedCap CFR for MBS broadcast [RedCapMBS_Bcast] |
Qualcomm Incorporated, Ericsson, Verizon, FirstNet |
| R2-2306019 |
Relay based Positioning posSIB forwarding |
Ericsson |
| R2-2306038 |
On Releasing Cross-Carrier Scheduling Configuration |
Samsung |
| R2-2306146 |
Introduction of ‘multiple QoS’ class in positioning |
Samsung R&D Institute UK |
| R2-2306163 |
RRC segment transmission continuity |
Apple |
| R2-2306200 |
Configuration release of cross carrier scheduling |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306201 |
Support of releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306202 |
UE capability for releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306208 |
Discussion on UE behaviours of delay measurements upon MO updates |
Huawei, HiSilicon |
| R2-2306221 |
Introduction of ‘multiple QoS’ class in positioning |
Samsung R&D Institute UK, Ericsson, Huawei, HiSilicon |
| R2-2306516 |
Considerations on voice and video support for Relays |
Philips International B.V., MediaTek, Vivo, FirstNet, KPN, TNO, Kyocera |
| R2-2306534 |
GNSS LOS/NLOS assistance information, stage 3 details and corrections |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306535 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306536 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306537 |
GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306673 |
[AT122][405][POS] Yaw and APC in Rel-18 (Swift) |
Swift Navigation (Rapporteur) |
| R2-2306674 |
[AT122][406][POS] Positioning for remote UEs CR check (CATT) |
CATT |
| R2-2306762 |
[AT122][003][TEI18] Inter-frequency Measurements (CMCC) |
CMCC |
| R2-2306786 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306787 |
GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306788 |
GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] |
Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2306827 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2306828 |
Capabilities of L2 UE-to-network relay UEs for positioning [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2306829 |
Discussion on MBS CFR for Redcap UE |
NEC |
| R2-2306838 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2306839 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] |
MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2306860 |
Support of releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306861 |
UE capability for releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306881 |
LS on longer CG-SDT periodicities |
Ericsson |
| R2-2306901 |
LS on longer CG-SDT periodicities |
Ericsson |
| R2-2306904 |
LS on longer CG-SDT periodicities |
RAN2 |
| R2-2306929 |
Support of releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| R2-2306930 |
UE capability for releasing crossCarrierSchedulingConifig |
Huawei, HiSilicon, Telecom Italia, China Unicom |
| 7.25.1 |
RAN4 led items |
|
| R2-2304636 |
LS on FR2 unknown SCell activation enhancement (R4-2306321; contact: Apple) |
RAN4 |
| R2-2304640 |
LS on RS supported for group-based reporting (R4-2306394; contact: Ericsson) |
RAN4 |
| R2-2304641 |
LS on MAC-CE Based Indication for Cross-RRH TCI State Switch (R4-2306399; contact: Nokia) |
RAN4 |
| R2-2304642 |
LS on non-simultaneous UL and DL from different two bands during UL CA (R4-2306465; contact: Nokia) |
RAN4 |
| R2-2304643 |
Response LS on extending the maximum range for NS values (R4-2306560; contact: Apple) |
RAN4 |
| R2-2304644 |
LS on lower MSD capability (R4-2306594; contact: Huawei) |
RAN4 |
| R2-2304672 |
Discussion on MSD Capability |
OPPO |
| R2-2304878 |
Non-simultaneous UL and DL from different two bands during UL CA |
Nokia, Nokia Shanghai Bell |
| R2-2304879 |
Lower MSD capability |
Nokia, Nokia Shanghai Bell |
| R2-2304880 |
Finalization of RAN2 work for MG enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2304925 |
Correction on 38.300 for BWP Wor |
vivo, Guangdong Genius |
| R2-2304926 |
Correction on 38.331for BWP Wor |
vivo, Guangdong Genius |
| R2-2304927 |
Correction on 38.306 for BWP Wor |
vivo, Guangdong Genius |
| R2-2305036 |
Discussion on RAN4 LS on MAC-CE Based Indication for Cross-RRH TCI State Switch |
Ericsson |
| R2-2305037 |
Draft CR to MAC spec changes on Cross-RRH TCI State Switch indication |
Ericsson |
| R2-2305038 |
Draft LS reply to RAN4 LS R4-2306399 |
Ericsson |
| R2-2305050 |
RAN2 Impacts of Cross-RRH TCI State Switch |
vivo Mobile Com. (Chongqing) |
| R2-2305106 |
Addition of extended NS value range |
Apple Inc |
| R2-2305107 |
Addition of extended NS value range |
Apple Inc |
| R2-2305204 |
Discussion on the support of Air to ground access |
Qualcomm Incorporated |
| R2-2305399 |
Consideration on non-simultaneous UL and DL in UL CA |
ZTE Corporation, Sanechips |
| R2-2305405 |
Discussion on no-gap measurement without interruption |
ZTE Corporation, Sanechips |
| R2-2305406 |
Discussion on FR2 unknown SCell activation enhancement |
ZTE Corporation, Sanechips |
| R2-2305414 |
Discussion on non-simultaneous UL and DL from different two bands during UL CA |
vivo |
| R2-2305428 |
Discussion on FR2 unknown SCell activation enhancement |
vivo |
| R2-2305476 |
Measurement reporting for FR2 unknown SCell |
LG Electronics Inc. |
| R2-2305733 |
Discussion on the support of ATG |
Xiaomi |
| R2-2305843 |
Support of lower MSD capability |
Ericsson |
| R2-2306017 |
Discussion on FR2 unknown SCell activation enhancement |
Ericsson |
| R2-2306062 |
Introduction of capability for inter-RAT LTE measurements without gap or interruption |
Huawei, HiSilicon |
| R2-2306091 |
Discussion on non-simultaneous UL and DL from different two bands during UL CA |
Huawei, HiSilicon |
| R2-2306104 |
Discussion on MAC-CE based indication for cross-RRH TCI state switch |
Huawei, HiSilicon |
| R2-2306164 |
FR2 SCell Enhancement |
Apple |
| R2-2306165 |
Draft LS reply on on FR2 unknown SCell activation enhancement |
Apple |
| R2-2306175 |
Discussion on non-simultaneous UL and DL from different two bands during UL CA |
CATT |
| R2-2306190 |
Discussion on RAN4 LS on FR2 unknown SCell activation enhancement |
Huawei, HiSilicon |
| R2-2306213 |
Discussion on Lower MSD Signalling |
vivo |
| R2-2306280 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306282 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306283 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306284 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306308 |
Consideration on Lower MSD Capability Signaling |
ZTE Corporation, Sanechips |
| R2-2306328 |
Correction on 38.306 for BWP Wor |
vivo, Guangdong Genius |
| R2-2306367 |
Cross RRH TCI state switch |
Nokia, Nokia Shanghai Bell |
| R2-2306368 |
Scell activation and L3 reporting |
Nokia, Nokia Shanghai Bell |
| R2-2306375 |
Discussion on the lower MSD capability |
Xiaomi |
| R2-2306513 |
Discussion on lower MSD capabilities |
Huawei, HiSilicon |
| R2-2306566 |
[DRAFT] Reply LS on non-simultaneous UL and DL from different two bands during UL CA |
Nokia |
| R2-2306567 |
Reply LS on MAC-CE Based Indication for Cross-RRH TCI State Switch |
RAN2 |
| R2-2306767 |
Addition of extended NS value range |
Apple Inc |
| R2-2306768 |
Addition of extended NS value range |
Apple Inc |
| R2-2306772 |
Reply LS on Lower MSD Capability Signaling |
Huawei |
| R2-2306779 |
Addition of extended NS value range |
Apple Inc |
| R2-2306780 |
Addition of extended NS value range |
Apple Inc |
| R2-2306802 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306803 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306804 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306805 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2306823 |
Draft LS reply on FR2 unknown Scell activation enhancement |
Apple |
| R2-2306862 |
Reply LS on non-simultaneous UL and DL from different two bands during UL CA |
RAN2 |
| R2-2306863 |
LS reply on FR2 unknown Scell activation enhancement |
RAN2 |
| R2-2306865 |
Reply LS on MAC-CE Based Indication for Cross-RRH TCI State Switch |
RAN2 |
| R2-2306866 |
Reply LS on Lower MSD Capability Signaling |
RAN2 |
| R2-2306876 |
Reply LS on measurements without gap |
RAN2 |
| R2-2306905 |
Reply LS on measurements without gap |
RAN2 |
| R2-2306918 |
LS reply on FR2 unknown Scell activation enhancement |
RAN2 |
| R2-2306919 |
Reply LS on measurements without gap |
RAN2 |
| 7.25.2 |
RAN1 led items |
|
| R2-2304645 |
LS on Rel-18 Tx switching across 3/4 bands (R4-2306623; contact: China Telecom) |
RAN4 |
| R2-2304671 |
Discussion on R18 UL Tx Switching |
OPPO |
| R2-2305242 |
Discussion on Rel-18 UL Tx Switching |
CATT |
| R2-2305339 |
discussion on UL tx switching |
vivo |
| R2-2305398 |
Discussion on Rel-18 UL Tx switching capability |
ZTE Corporation, Sanechips |
| R2-2305844 |
Fallback compatibility for UL Tx switching Rel-18 |
Ericsson |
| R2-2306172 |
Leftover issues in UL Tx switching |
Apple |
| R2-2306186 |
RRC configuration for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2306187 |
UE capability reporting for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2306188 |
UE capabilities of Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2306189 |
Remaining issues on RAN2 signalling design for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon |
| R2-2306432 |
Remaining issues on Rel-18 UL Tx switching |
NTT DOCOMO INC. |
| R2-2306911 |
RRC configuration for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2306912 |
UE capability reporting for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2306913 |
UE capabilities of Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon, NTT DOCOMO INC. |
| 7.25.3 |
Other |
|
| R2-2304603 |
Reply LS on 3GPP work on Energy Efficiency (C1-232650; contact: Huawei) |
CT1 |
| R2-2304604 |
Reply LS on Research highlighting potential 5G and 4G Bidding Down Attacks (C1-232756; contact: Ericsson) |
CT1 |
| R2-2304606 |
LS on NAS-AS interaction in terms of NS-AoS (C1-232944; contact: Nokia) |
CT1 |
| R2-2304607 |
Reply LS on 3GPP work on Energy Efficiency (C3-231470; contact: Huawei) |
CT3 |
| R2-2304653 |
Reply LS on Support of network slices which have area of service not matching deployed tracking areas (S2-2306045; contact: Ericsson) |
SA2 |
| R2-2304654 |
Reply LS on partially allowed/rejected S-NSSAI (S2-2306254; contact: Nokia) |
SA2 |
| R2-2304778 |
Remaining issues on Further Enhancement NPN |
CATT |
| R2-2305140 |
Discussion on RAN impacts of further NPN enhancement |
Lenovo |
| R2-2305345 |
Draft CR of new location information type for PRU |
vivo |
| R2-2305416 |
Reply LS proposal for C1-232944/R2-2304606 (LS on NAS-AS interaction in terms of NS-AoS) |
Nokia, Nokia Shanghai Bell |
| R2-2306024 |
On the Positioning Reference Units aspects |
Ericsson |
| R2-2306073 |
Discussion on RAN impact for NPN enhancement in Rel-18 |
Huawei, HiSilicon |
| R2-2306178 |
Discussion on further enhancement of NPN in R18 |
China Telecom |
| R2-2306179 |
Draft CR to TS 38.304 on introduction of R18 eNPN |
China Telecom, ZTE Corporation, Sanechips, CATT, Huawei, HiSilicon |
| R2-2306180 |
(draft CR to TS 38.300) On introduction of R18 eNPN |
China Telecom, ZTE Corporation, Sanechips, CATT |
| R2-2306214 |
Discussion on further enhancement of private network support for NG-RAN |
vivo |
| R2-2306441 |
Discussion for NPN Rel-18 |
Ericsson |
| R2-2306442 |
38.300 DraftCR for NPN Rel-18 |
Ericsson |
| R2-2306443 |
38.304 DraftCR for NPN Rel-18 |
Ericsson |
| R2-2306444 |
38.331 DraftCR for NPN Rel-18 |
Ericsson |
| R2-2306454 |
(draft CR to TS 38.331) On support of equivalent SNPN |
China Telecom |
| R2-2306801 |
Draft CR to TS 38.304 on introduction of R18 eNPN |
China Telecom, ZTE Corporation, Sanechips, CATT, Huawei, HiSilicon |
| R2-2306821 |
Reply LS on NAS-AS interaction in terms of NS-AoS |
RAN2 |
| R2-2306832 |
(draft CR to TS 38.331) On support of equivalent SNPN |
China Telecom |
| R2-2306882 |
Response LS on Partially Allowed/Rejected S-NSSAI |
RAN3 |
| 7.25.4 |
Self-Evaluation NTN |
|
| R2-2305198 |
RAN2 aspects on evaluation methodology for IMT-2020 Satellite |
Qualcomm Incorporated |
| R2-2305410 |
Discussion on IMT-2020 Satellite self-evaluation for Latency and Mobility |
THALES |
| R2-2305965 |
Self Evaluation for NR NTN |
Huawei, HiSilicon |
| R2-2306469 |
Satellite IMT-2020 RAN2 aspects |
Ericsson |
| 8.1 |
Session on NR NTN and IoT NTN |
|
| R2-2306541 |
Report from Break-Out Session on NR NTN and IoT NTN |
Vice Chairman (ZTE) |
| 8.2 |
Session on LTE legacy, XR, QoE and Multi-SIM |
|
| R2-2306542 |
Report from session on LTE legacy, XR, QoE and Multi-SIM |
Vice Chairman (Nokia) |
| 8.3 |
Session on UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
|
| R2-2306543 |
Report from UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
Session chair (InterDigital) |
| 8.4 |
Session on positioning and sidelink relay |
|
| R2-2306544 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 8.5 |
Session on LTE V2X and NR SL |
|
| R2-2306545 |
Report from session on LTE V2X and NR SL |
Session chair (Samsung) |
| 8.6 |
Session on SON/MDT |
|
| R2-2306546 |
Report from SON/MDT session |
Session chair (CMCC) |
| 8.7 |
Session on MBS |
|
| R2-2306547 |
Report from MBS breakout session |
Session chair (Huawei) |
| 8.8 |
Session on IDC |
|
| R2-2306548 |
Report from IDC breakout session |
Session chair (Intel) |
| 8.9 |
Session on NC Repeater |
|
| R2-2306549 |
Report from NC Repeater breakout session |
Session chair (Apple) |
| 8.10 |
Session on eRedCap |
|
| R2-2306550 |
Report from eRedCap breakout session |
Session chair (Ericsson) |
| 8.11 |
Session on Further NR coverage enhancements |
|
| R2-2306551 |
Report from Further NR coverage enhancements session |
Session chair (ZTE) |
| 8.12 |
Session on NR MIMO evolution |
|
| R2-2306552 |
Report from NR MIMO evolution session |
Session chair (CATT) |